zone disappearing and then not resolving
nate at wired.com
Mon Feb 25 18:33:28 UTC 2002
On Mon, Feb 25, 2002 at 04:38:41PM +0000, Brian Hardy wrote:
> Every few months, on our DNS server (UNIX) we start getting the error
> message in "/var/adm/messages" :
> /usr/local/etc/named.conf:xxx: syntax error near "}" where "xxx" is the
> line number.
> eventually, after several days of the aforementioned error first
> appearing, the zone directly below it stops resolving...
> How can this error persist for several days, the domain is question still
> resolving perfectly, and then after several days, the domain stops
> resolving...is there a limit on the # of times that error message appears
> in "/var/adm/messages" and once that limit is reached, the domain breaks?
Some or all zones were no longer being loaded on your master server, so
your slaves couldn't update their copy of the zone. After the designated
expire interval, your slaves then expired the zone(s).
The records in your zone(s) would still resolve correctly on the slaves
up until they expired the zone(s).
Fix named.conf (you probably need to add a semicolon after the curly
brace on the line mentioned in the logs).
Nate Campi Job: hostmaster at lycos.com and root at wired.com
Programmer /n./ A red-eyed, mumbling mammal capable of conversing with
More information about the bind-users