What does "update failed foo.com 2" mean ?

Pete Ehlke pde at ehlke.net
Sat Aug 31 04:06:01 UTC 2002


On Thu, Aug 29, 2002 at 11:57:09PM +0100, Jonathan de Boyne Pollard wrote:
> 
> l> [...] there was only that domain's NS record in my cache, while no
> l> A record of that domain's name server, in other words, these A
> l> record expired before the NS record did.
> l> [...] next time when a name which belongs to that domain got
> l> resolved, [...] the named forwarded this request to the root server.
> l> The root server replied with a package including two NS record and
> l> one A record . Then [...] the error "update failed foo.com 2"
> l> appeared. We couldn't resolve all those names belongs to that domain
> l> until the NS record got expired either.
> 
> This sounds very much like the scenario given in the description of one
> particular BIND bug at
> <URL:http://cr.yp.to/djbdns/bugtraq/20000112082807-15140-qmail@cr-yp-to>.

Congratulations, Jonathan. A month late, you post a contentless message
that nonetheless manages to be snide and condescending. If you
genuineley think there's a bug here, file a bug report with
bind-bugs at isc.org or bind9-bugs at isc.org. Don't forget your
documentation and evidence.

-P.


More information about the bind-users mailing list