I have a very strange intermittent issue with BIND. I am running a redhat server (although my Gentoo boxes do the same thing periodically) and every once in awhile if you change the zone file in any way, it suddenly wont respond to queries. When you try:
dig @DNSServer localDomainHostName
it give you NXDOMAIN for a status. Now this has been happening for years, and it always seems to fix itself at some point, but it always seems to take different things to fix it.
One time I just had to change the owner of the file MYDOMAIN.db and MYDOMAIN.db.jnl to named:named from root:root. But for example today, that didn't do it. I know that my configuration is OK, since it has worked for months now without a hitch (they all do). But then I add one extra static A record to my MYDOMAIN.db file, and suddenly the whole thing stops responding to any localdomain queries. While still serving its forwarding role just fine.
What makes it even more confounding is that it doesnt seem to matter whether I use the redhat GUI for DNS, or if I use VI to edit the file in a bash prompt. Or which OS I'm using. Its one of the most elusive and annoying problems I have ever encountered.
Has anyone else ever encountered anything like what I'm talking about, or know any tricks to see where the system might be getting caught? Its starting to become annoying to have to just keep spending random afternoons resetting everything and messing with every file in sight until suddenly out of the blue it starts working again.