NS and recursive? query

Mike Machado mike at innercite.com
Mon Sep 6 11:05:24 UTC 1999


Michael Voight wrote:

> Mike Machado wrote:
> >
> > Ok , this should be an easy answer to any experienced DNS admin.
> > I have two servers, and countrydog.com domain.
> >
> > Say the internic is pointed to server 1 for this domain but the actual
> > resource records are on server 2. What I have is on server 1:
> >
> > @                    server1.innercite.com.    root.countrydog.com. (
> >                 1999090501      ; serial number
> >                 10800           ; secondary refresh interval
> >                 3600            ; secondary retry interval
> >                 864000          ; secondary expire after about 10 days
> >                 3600  )         ; TTL
> >
> >                 IN      NS   server2.innercite.com.
> >
>
> NO NO NO...
>
> This means server 1 is authoritative and is expected to have all of the
> records. If a server is authoritative and you query it for something it
> doesn't have, you will get NXDOMAIN.
>

How does the internic manage to not be authorative and not be a secondary?
Isn't this what I would need to do for this to work?

>
> Why not make it secondary to server 2? What is the purpose here?

I want all queries coming to server1 to be asked on server 2 immidiatly.
Having it a secondary would make it so if I changed a RR on server 2 it
would have to wait until it detected the zone had been changed. Maybe a
NOTIFY to server 1 from server2 when server2 changes the dns? This will
trigger server 1 to do an immidiate zone transfer right?

>
> You do NOT make a server authoritative for a zone, unless you consider
> it to be the LAST source you will query for the info. This means it MUST
> have all the records you expect to resolve when you query it.
>
> Michael

--
Mike Machado
mike at innercite.com
InnerCite
Network Specialist





More information about the bind-users mailing list