Slack Blocks OpenDNS
When I use OpenDNS in Chrome, slack.com doesn't resolve. None of the other DNS services block Slack.
dig @208.67.222.222 +noall +answer -t ns slack.com
slack.com. 1613 IN NS ns-166.awsdns-20.com.
slack.com. 1613 IN NS ns-606.awsdns-11.net.
slack.com. 1613 IN NS ns-1493.awsdns-58.org.
slack.com. 1613 IN NS ns-1901.awsdns-45.co.uk.
dig @208.67.222.222 +noall +answer -t a slack.com
slack.com. 60 IN A 35.82.91.193
slack.com. 60 IN A 44.234.235.93
slack.com. 60 IN A 44.237.180.172
slack.com. 60 IN A 52.89.90.67
slack.com. 60 IN A 54.70.179.16
slack.com. 60 IN A 54.71.95.193
slack.com. 60 IN A 54.188.33.22
slack.com. 60 IN A 54.245.50.245
slack.com. 60 IN A 35.81.85.251
dig @208.67.220.220 +noall +answer -t ns slack.com
slack.com. 288 IN NS ns-166.awsdns-20.com.
slack.com. 288 IN NS ns-606.awsdns-11.net.
slack.com. 288 IN NS ns-1493.awsdns-58.org.
slack.com. 288 IN NS ns-1901.awsdns-45.co.uk.The only difference I see when I query OpenDNS vs CF and Google is that the EDNS packet size returned from CF is 1232 from dns flag day, Google is 512 and OpenDNS is 4096. I was going to test with the EDNS validator but that is meant for authoritative servers and chokes on recursive. Using this tool [3] with OpenDNS and Slack I get back a lot more IP's. Maybe that is what Chrome is choking on.
Another thing to try is this [2] Go to chrome://flags and search for dns and disable the "Built-in Asynchronous DNS"
[1] - https://windowsreport.com/chrome-failed-to-load-response-dat...
https://support.opendns.com/hc/en-us/community/posts/1150077...