I don't know what could be causing this.. or how this symptom even comes to be. All I know is it started after the last server move.
I still periodically get errors where the hostname can not be resolved. This happens from both work (AT&T DNS servers) and from home (cable modem and Adelphia DNS servers). I also have access to another DNS server which runs from its own root hints file.
The situation is typically clicking on the URL in notification emails. The site can not be resolved. Trying again from within the browser does not work. But using the IP instead of the hostname does work, so I know the website is up.
Typically I'll try a nslookup from the computer, using its default DNS lookups, and it will fail. But after hitting the website via IP, normally the DNS lookup succeeds! And any browser links work after that.
I haven't done a dig or anything on the domain yet to look at its configuration.. but this is the only site where I have this problem. And I get it from multiple networks (with their own DNS servers).
Next steps are to compare the configs and look at the path between me and the DNS servers to ensure I can actually hit those servers when the failure occurs.. but this is very strange.
No way this is propogation errors, etc unless the domain has some rediculous TTLs configured.
Anyone else see this.. MonorailMan.. any input? I can start doing more diag, but figured I'd see if I was alone first.