$INCLUDEing an SOA record

[Jim Reid]

>>>>> "chris" == chris  <chris at monmouth.com> writes:

    chris> The serial HAS changed.  The SOA is in the included file.
    chris> If it was one bog file, it would have reloaded.  That's
    chris> what's so perplexing.

Just a guess.....

You have a zone file which $INCLUDEs another file containing the SOA
record (yuk!). When BIND loads a zone file, it remembers the time it
did that and the date the file was last changed. It probably doesn't
see the changed SOA record because it's not in the zone file given in
the coresponding zone{} statement in named.conf. As far as the name
server is concerned the zone hasn't changed because the zone file
hasn't been updated since the last time the server loaded it.

You probably should stick to having exactly one zone file for each
zone. Life is a lot easier for everyone that way. I suspect the above
scenario explains one of the reasons why one zone, one file is a good
idea. Having all your zone files share the same SOA record is messy
and clumsy, but you probably know that now. :-)