Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've got a nameserver that I updated a zone file on, incremented the serial, and ran rndc reload. I then verified that named saw it in the log, and it did, without errors. But when I run dig domain.tld @localhost note: @localhost is the bind server I made the changes on. bind still see's the old A record, in its cache. Do I misunderstand how bind works? or is this a problem?

share|improve this question
    
So I sorta figured this one out... upon further investigation by a co-working some ACL or something was preventing the query and thus we were getting a cached result. –  xenoterracide Nov 5 '10 at 23:34
add comment

1 Answer

up vote 1 down vote accepted

According to the BIND Administrator's Reference Manual, reload reloads configuration files and zones. Only. Verify that you get the response from the correct nameserver.

share|improve this answer
    
well considering localhost is the nameserver and I did it @localhost. so according to the manual it wouldn't clear the cache for that zone, if I understand what you're saying correctly? –  xenoterracide Oct 29 '10 at 9:35
    
It does not cache information for master zones. There is something wrong with either your named.conf (is it declared as a master zone?) or with the SOA and/or NS RRs of your zone. –  adamo Oct 29 '10 at 10:31
    
I don't remember, don't think so, it was probably a cpanel addon domain. We never edit named.conf. I know it was only an A record for a subdomain that I had updated. –  xenoterracide Oct 29 '10 at 12:06
    
Are we talking about your domain? For if we are, I see that it is delegated as a CNAME which makes it impossible to delegate any other information with it: zytrax.com/books/dns/ch8/cname.html - Can you post the relevant contents of the named.conf and the zone file? Even though you do not directly edit them. –  adamo Oct 29 '10 at 12:33
    
no we're not talking about my domain, and I couldn't post it. It's a customers domain at my job. tbh, I don't even know what account it is anymore, that was days ago. But I suspect the server was caching stuff it shouldn't have been. –  xenoterracide Nov 1 '10 at 9:24
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.