1.1.1.2 & 1.1.1.3 blocking Box connections

As part of using the Box client, it makes outbound connections to the host “ec2euc1.boxcloud.com” for some services. If you’re using 1.1.1.1 for Families, this looks to be getting filtered in DNS and/or is returning different results which breaks the Box client. Using standard 1.1.1.1 works as expected.

[email protected]:~ % host ec2euc1[.]boxcloud[.]com 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
ec2euc1[.]boxcloud[.]com is an alias for wildcard[.]boxcloud[.]com.
wildcard[.]boxcloud[.]com has address 185.235.236.200

[email protected]:~ % host ec2euc1[.]boxcloud[.]com 1.1.1.2
Using domain server:
Name: 1.1.1.2
Address: 1.1.1.2#53
Aliases:
ec2euc1[.]boxcloud[.]com has address 0.0.0.0
ec2euc1[.]boxcloud[.]com has IPv6 address ::
ec2euc1[.]boxcloud[.]com is an alias for wildcard[.]boxcloud[.]com.

[email protected]:~ % host ec2euc1[.]boxcloud[.]com 1.1.1.3
Using domain server:
Name: 1.1.1.3
Address: 1.1.1.3#53
Aliases:
ec2euc1[.]boxcloud[.]com has address 0.0.0.0
ec2euc1[.]boxcloud[.]com has IPv6 address ::
ec2euc1[.]boxcloud[.]com is an alias for wildcard[.]boxcloud[.]com.
[email protected]:~ %

(I’ve had to modify the hostnames as it won’t let me post otherwise)

That hostname is flagged as malware. I’m not completely surprised, as anything can be on it, but you can request to recategorize it:
https://radar.cloudflare.com/domain/ec2euc1.boxcloud.com

Thanks. I’ve submitted an update

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.