Fwd: RE: Problem to add new domains!

[Éric Allard]

>Date: Mon, 18 Feb 2002 10:41:52 -0500
>From: Drew Weaver <drew.weaver at thenap.com>
>Subject: RE: Problem to add new domains!
>To: '=C9ric Allard' <bind_ml at telusquebec.net>
>X-Mailer: Internet Mail Service (5.5.2653.19)


This entry has been previously entered in the named.conf like the following:

zone "newdomain.com" {
         type slave;
         file "cpie1/newdomain.com";
         masters {
                 199.123..34.43;
         };
};

>Uhh you need to put an entry for secondary in your named.conf on the
>secondary box.
>
>-Drew
>
>
>-----Original Message-----
>From: =C9ric Allard [mailto:bind_ml at telusquebec.net]
>Sent: Monday, February 18, 2002 10:31 AM
>To: bind-users at isc.org
>Subject: Problem to add new domains!
>
>
>
>We use bind 8.2.5 on solaris!
>
>When we add new domains in our primary (master) DNS, this DNS sends a
>notify to our secondary (slave) DNS. This is all right!
>When the secondary (slave) DNS receives this "notify", it answers "name not
>one in our zones". It answers it even if we already
>have autority of these domains.
>
>Here an example of the log in our master DNS:
>
>Feb 18 09:19:14 masterdns named[21219]: Sent NOTIFY for "newdomain.com IN
>SOA 2002021801" (newdomain.com); 2 NS, 2 A
>
>Here the log in our slave DNS:
>
>rcvd NOTIFY(newdomain.com, IN, SOA) from [masterdns].56516
>Feb 18 09:19:03 slavedns named[1797]: [ID 295310 local0.info] rcvd NOTIFY
>for "newdomain.com", name not one of our zones
>
>Here the entry in our named.conf about this domain:
>
>zone "newdomain.com" {
>          type master;
>          file "cpie1/newdomain.com";
>};
>
>Why the slave always answer this error name instead of adding this newly
>entry?
>
>I would appreciate any hints!
>Thank you very much in advance!