Why has my network stopped resolving certain DNS routes?
Posted on 2009-02-17
We have an S3 account where we store the content for our website. Yesterday, I noticed that the content isn't working, so I started looking into it. I found out that the DNS is pointing to the correct place, and the DNS host said that the request was being blocked somewhere between our router and the host. We put in a ticket with our ISP and they put in a ticket with theirs. Eventually, someone found the block and removed it.
Now, our nameserver is looking to itself to find the next server in the route, but since we flushed it and deleted the cache, it has no information to resolve. If we bypass the nameserver and set the nameserver as our ISP's nameserver, it resolves just fine. What can we do to get it working again? Yesterday, traceroute would get halfway and find the block, then get no response. Now, it gets "Unable to resolve target system name content.*********.com"