A user reported to me that they are unable to access rotary.org. This is a fairly major international site, so it seemed a bit strange. I replicated the issue on my machine in different browsers. Rotary.org results in a page not found error.
Our environment is two Windows Server 2008 R2 DCs running DNS for the campus. They are each configured to use root hints, with no DNS forwarders in use. The systems are solid, and for other parts of the internet, they seem to resolve DNS queries like a champ. All campus computers are set to use these DCs as DNS servers, and except for the DCs, workstations cannot make outside DNS requests (blocked by firewall).
This problem comes and goes. In the past, I have flushed the DNS cache on both servers as a temporary fix. When the issue is happening, performing an nslookup results in something like the following (simulated, since the issue isn't present right now): nslookup Default Server: dc1.zzz.edu Address: 192.168.2.4
> rotary.org Server: dc1.zzz.edu Address: 192.168.2.4 *** dc1.zzz.edu can't find rotary.org: Server failed
When it does work:
nslookup Default Server: dc1.zzz.edu Address: 192.168.2.4 > rotary.org Server: dc1.zzz.edu Address: 192.168.2.4 Non-authoritative answer: Name: rotary.org Address: 126.96.36.199
Flushing the DNS cache on the server resolves this - usually - instantly. intoDNS DNS report shows that most things on their end are normal: http://www.intodns.com/rotary.org EXCEPT that they provide no glue between their name servers.
This issue appears to be only for rotary.org - no other users have reported issues. I'm fine clearing the cache when there is an issue, but I'd also like to understand what could be causing this. Could this issue be on our end, or does rotary.org pass some funky DNS?