serial error with zone transfers

[Charlie Clemmer]

I'm not Michael, but I've seen the same behavior.

On my remote secondary, I get the error message "Err/TO getting serial#
for "domain.com", where domain.com is any and all domains that the
secondary is carrying. According to the URL you listed, this means that
either a router somewhere is consuming traffic to TCP port 53, or this
zone has been deleted from the master. 

What's interesting....if I make a change to one of the zone files on the
master, increase the serial number, and restart the server, my
secondaries are notified of the change, and they correctly transfer the
updated zone information. The error message listed above only shows up
some days after the successful zone update.

Charlie

Barry Margolin wrote:
> 
> In article <390a2b07.46135418 at nntp.infoave.net>,
> Michael Long <mlong at nospam.infoave.net> wrote:
> >We run a pretty tight ship, but we also server as secondary for other
> >zones out there...and they always no doubt call us to ask why their
> >zones won't transfer properly to us.  When we look in our logs, all we
> >get is a message indicating that there is an error with the serial.
> >When we look at the zone file on the other server, the serial number
> >looks fine.  Can anyone give me some hints?  We run 8.2.2P5
> 
> Unless you tell us what the error message says, I don't see how we can.
> 
> Why don't you look the error message up on the BIND warnings web page,
> <http://www.acmebw.com/askmrdns/bind-messages.htm>?
> 
> --
> Barry Margolin, barmar at genuity.net
> Genuity, Burlington, MA
> *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
> Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.