secondary dns acting up

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Tue Sep 19 11:27:02 UTC 2000


	If you have a old enough version this could be the problem.

 433.   [bug]           req_notify required the slave zone to have been loaded.
                        this may not be the case when a zone has expired or
                        is being established over a dial on demand link.

	Mark

> 
> on 19/09/00 12:59, Jim Reid at jim at rfc1035.com wrote:
> 
> >>>>>> "Thomas" == Thomas von Hassel <t at garbage.dk> writes:
> > 
> > Thomas> Hi im having a few problems with my secondary dns. After i
> > Thomas> put a new server on the network it refuses to accept
> > Thomas> NOTIFY's from my master dns.
> > 
> > Thomas> Sep 19 11:41:11 jerry named[16760]: rcvd NOTIFY(domain.dk, IN, SOA)
> > from [xxx.xxx.xxx.x].1073
> > Thomas> Sep 19 11:41:11 jerry named[16760]: rcvd NOTIFY for "domain.dk", na
> me
> > not one of our zones
> > 
> > Show the config files and real names and IP addresses! Why hide useful
> > information that would help to identify the source of the problem?
> > 
> > Something at address xxx.xxx.xxx.x sent a NOTIFY message for the
> > domain.dk zone (grr!) from port 1073 to your server. Your server does
> > not believe that it is a slave (secondary) server for that zone. There
> > are two explanations.
> > [1] The owner of domain.dk has screwed up by falsely claiming your
> > server slaves that zone.
> > [2] You've screwed up by not configuring you server as a slave for
> > domain.dk.
> > 
> > Since you hid the IP address and the actual domain name - all the
> > servers for the real domain.dk zone are answering authoritatively -
> > it's hard to say exactly where the fault lies.
> > 
> > Next time, supply the actual IP addresses and domain names. That
> > allows someone to interrogate the name servers, check out the
> > delegations, etc, etc. When you're ill, do you just tell the doctor
> > "I'm sick" or "my back hurts" when you've actually got a headache?
> > Would you expect your doctor to diagnose the problem when you don't
> > tell them what's actually wrong?
> 
> On the slave:
> 
> zone "linkweb.dk"{
>         type slave;
>         file "secondary/linkweb_2";
>         masters{212.130.193.2; };
> };
> 
> SOA:
> 
> linkweb.dk
>         origin = ns.linkweb.dk
>         mail addr = thomas.linkweb.dk
>         serial = 2000091902
>         refresh = 28800 (8H)
>         retry   = 14400 (4H)
>         expire  = 3600000 (5w6d16h)
>         minimum ttl = 864000 (1w3d)
> linkweb.dk      nameserver = ns.linkweb.dk
> linkweb.dk      nameserver = ns2.linkweb.dk
> ns.linkweb.dk   internet address = 212.130.193.2
> ns2.linkweb.dk  internet address = 212.130.193.3
> 
> If i have more than one zone in /etc/named.conf on the master, do i need to
> speciafy them as slaves also on the slave ?. until now it has worked fine
> with the current setup....
> 
> /thomas
> ...
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com



More information about the bind-users mailing list