BIND Stops Listening on TCP/53
Tim Wilde
twilde at dyndns.com
Fri Jan 6 17:35:00 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 6 Jan 2006, Barry Margolin wrote:
> Are there any log messages from named saying that it updated its
> interface info, or couldn't bind for some reason?
None that I'm aware of. However, I'm not 100% sure when it happened, as
we weren't previously monitoring TCP/53 specifically, we only found out
about this when customers had problems with registrars that require all
servers they're delegating to listen on TCP/53. We've begun monitoring it
now (and gotten some requests from Mark to capture debugging information
if/when it happens again), so hopefully we'll be able to hunt down the
cause.
Thanks,
Tim Wilde
- --
Tim Wilde
twilde at dyndns.com
Systems Administrator
Dynamic Network Services, Inc.
http://www.dyndns.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFDvqpGT9UHzqLr6x4RAkabAJ9JXBbMheWdNAnzWDnmEFtLR5rJTwCglkqQ
Jm99f9r56o2xe2LUg9R6+Q0=
=cJGD
-----END PGP SIGNATURE-----
More information about the bind-users
mailing list