Not authoritative in internal view (Was: Re: Server Not Authoratative)
Eric Pancer
epancer at gmail.com
Thu Sep 15 07:53:09 UTC 2005
Actually, something strange is the following...
# tail /var/log/messages
Sep 15 02:33:22 ns1 named[24736]: starting BIND 9.3.0
Sep 15 02:33:22 ns1 named[24736]: command channel listening on 127.0.0.1#953
Sep 15 02:33:22 ns1 named[24736]: command channel listening on ::1#953
Sep 15 02:33:23 ns1 named[24736]: client 2001:4830:2280::53#43397: view
internal: received notify for zone 'ipv6.nxio.us <http://ipv6.nxio.us>': not
authoritative
Sep 15 02:33:23 ns1 named[24736]: client 207.227.243.194#42989: view
internal: received notify for zone 'ipv6.nxio.us <http://ipv6.nxio.us>': not
authoritative
Sep 15 02:37:07 ns1 named[24736]: client 2001:4830:2280::53#6029: view
internal: received notify for zone 'ipv6.oak.nxio.us<http://ipv6.oak.nxio.us>':
not authoritative
Sep 15 02:37:07 ns1 named[24736]: client 207.227.243.194#43037: view
internal: received notify for zone 'ipv6.oak.nxio.us<http://ipv6.oak.nxio.us>':
not authoritative
Seems that my internal view can't get refreshed on the same server that is
holding the external authoritative data. Can anyone comment on if this is a
normal error? When I query from the outside after refreshing the serial
number and reloading the zone, I get the updated serial. But when querying
from the cache on the nameserver itself, I get an older serial. Even
stopping the server completely and restarting it seems to keep the old
serial lingering around.
Thanks.
More information about the bind-users
mailing list