Quote Originally Posted by Relena Peacecraft View Post
UPDATE: It actually seems that any domain using the same dns servers as EoFF sees the same behavior. Since this appears to mostly be a bunch of no-name sites, no wonder I wouldn't notice. Therefore, I must hypothesize that this is a communication problem between some of google's DNS servers and the godaddy dns servers. Presumably it will resolve someday if someone notices. I have no idea if this information applies to Aaron's problem whatsoever.
Are you configured somehow to not accept non-authoritative name resolutions? I don't really know how this would be done (conceivably it's something configurable in Linux) but it's possible that it isn't accepting a non-authoritative answer, and is then checking in for an authoritative one, but can't reach that name server. Maybe none of that even makes sense at all to someone with more knowledge than me about DNS, I'm not really an expert.

The more likely explanation though is that GoDaddy's cheap/free DNS sucks a lot, and is returning periodic non-existent domain responses, which then get cached for a while somewhere.

EDIT:

What happens when you do this (at a time the problem is happening)?
nslookup forums.eyesonff.com ns01.domaincontrol.com
or
nslookup forums.eyesonff.com ns02.domaincontrol.com

Since those are the actual name servers EoFF is using, they should be the ones returning the actual result?