Old zones work, new ones don't

[Danny Mayer]

What does syslog tell you about these zones?  If you are running these
zones as slaves to a master elsewhere, you may find that it is unable
to transfer the zones from the master. You need to check that the
master is allowing your server to transfer the zones. SERVFAIL usually
happens on a slave zone because the server has been unable to get
updated zone information from the master within the expire period
specified in the SOA record.

         Danny
At 04:25 PM 1/8/02, Cody wrote:

>First of all, I've searched all over the Internet for an answer to
>this question, and still can't find one, so that's why I'm posting
>this message.  I'm running a DNS server on a Linux box.  I'm the
>server for 12 domains, but that number used to be 6.  When I was the
>server for the 6 domains, things ran fine.  I added 6 new zone files
>to /var/named and also added the entries in the named.conf file.
>Those entries were exactly like the prior ones, and the zone files
>were identical, except for the fact that certain domains are pointing
>to different IPs.  The problem is, when I restart BIND, it doesn't
>notify for the 6 new domains, and when I dig those domains from the
>localhost DNS server, I get a SERVFAIL error.  Permissions are
>correct, and I've tried everthing I can think of to fix this, all to
>no avail.  Any ideas?
>
>Thanks,
>Cody