3 ms·

Slack Blocks OpenDNS

5 points by b8 3y ago

When I use OpenDNS in Chrome, slack.com doesn't resolve. None of the other DNS services block Slack.

LinuxBender 3y ago
It appears to be working from my IP. Per nullindividual's comment do you have a special account setup with them? 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.
- b8 3y ago
  I don't have an account with OpenDNS. Simply using Chrome's OpenDNS option.
  - LinuxBender 3y ago
    Having never used Chrome I would be guessing here but there should be a web developer console option that should have options to enable debugging network traffic after clearing cache of course. Perhaps that might show more details about what is going on. Or if you are on Mac or Linux could you use the dig command from the above examples to see if your machine gets the right results and only the browser is having challenges?
    - b8 3y ago
      nslookup/ping works fine. I just see this under network in dev tools: "Failed to load response data: No resource with given identifier found". As soon as I selected any other DNS, and press f5 in Chrome it then loads perfectly.
      - LinuxBender 3y ago
        Interesting. Aside from trying the steps here [1] one thing I could suggest is to disable any addons, clear cache and see if that changes anything. Or if you have the Slack client which I think is based on Electron maybe that won't hit the same issue. 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-data/ https://windowsreport.com/chrome-failed-to-load-response-dat... [2] - https://superuser.com/a/804406 https://superuser.com/a/804406 [3] - https://dnslookup.online/ https://dnslookup.online/
nullindividual 3y ago
A two second search for 'opendns slack' yields this as the top result: https://support.opendns.com/hc/en-us/community/posts/115007774728-Working-wiht-SLACK-COM-services-and-Open-DNS-web-content-filtering https://support.opendns.com/hc/en-us/community/posts/1150077...

5 points by b8 3y ago

When I use OpenDNS in Chrome, slack.com doesn't resolve. None of the other DNS services block Slack.

It appears to be working from my IP. Per nullindividual's comment do you have a special account setup with them? 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.

b8 3y ago
I don't have an account with OpenDNS. Simply using Chrome's OpenDNS option.
- LinuxBender 3y ago
  Having never used Chrome I would be guessing here but there should be a web developer console option that should have options to enable debugging network traffic after clearing cache of course. Perhaps that might show more details about what is going on. Or if you are on Mac or Linux could you use the dig command from the above examples to see if your machine gets the right results and only the browser is having challenges?
  - b8 3y ago
    nslookup/ping works fine. I just see this under network in dev tools: "Failed to load response data: No resource with given identifier found". As soon as I selected any other DNS, and press f5 in Chrome it then loads perfectly.
    - LinuxBender 3y ago
      Interesting. Aside from trying the steps here [1] one thing I could suggest is to disable any addons, clear cache and see if that changes anything. Or if you have the Slack client which I think is based on Electron maybe that won't hit the same issue. 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-data/ https://windowsreport.com/chrome-failed-to-load-response-dat... [2] - https://superuser.com/a/804406 https://superuser.com/a/804406 [3] - https://dnslookup.online/ https://dnslookup.online/

nullindividual 3y ago

A two second search for 'opendns slack' yields this as the top result: https://support.opendns.com/hc/en-us/community/posts/115007774728-Working-wiht-SLACK-COM-services-and-Open-DNS-web-content-filtering https://support.opendns.com/hc/en-us/community/posts/1150077...