lookup error
Ramesh
rameshr_email at yahoo.com
Wed Jun 16 18:19:14 UTC 2004
I am using BIND 8.2.2-p5, nslookup fails sometimes soon after the
named is reloaded. ndc is used for reload. Is there a bug associated
with ndc or reload of named?
I see the following
1. DNS was working fine initially, I regenerated the zone files and
other DNS configuration files and reconfiged, reloaded named using
ndc. nslookup following the reload fails sometimes. The problem is
intermittent.
/var/adm/messages show
Jun 16 06:57:13 xxx named[28393]: [ID 295310 daemon.warning]
db.prot.net: WARNING SOA expire value is less than 7 days (57600
)
Jun 16 06:57:13 xxx named[28393]: [ID 295310 daemon.notice] reloading
nameserver
Jun 16 06:57:13 xxx named[28393]: [ID 295310 daemon.warning] db.root:
WARNING SOA expire value is less than 7 days (57600)
Jun 16 06:57:13 xxx named[28393]: [ID 295310 daemon.warning]
db.10.252.22: WARNING SOA expire value is less than 7 days (57600)
Jun 16 06:57:13 xxx named[28393]: [ID 295310 daemon.notice] Ready to
answer queries.
Jun 16 06:57:13 xxx named[28393]: [ID 295310 daemon.notice] reloading
nameserver
Jun 16 06:57:13 xxx named[28393]: [ID 295310 daemon.notice] Ready to
answer queries.
$ nslookup
*** Can't find server name for address 10.252.0.1: Non-existent
host/domain
*** Default servers are not available
More information about the bind-users
mailing list