Re: [cobalt-users] automatic secondary DNS caching

[Adam Williams <adam@xxxxxxxxxxxxxx>]

ns1.intop.net is 206.156.254.3 and its doping primary DNS correctly, and I
want to have ns2.intop.net (which is also a raq 3) at 206.156.254.9 do
secondary DNS by way of DNS caching the DNS files in /etc/named on the
primary nameserver.  I knot there is an also-notify line you can use in
named.conf and set ns2 to be a slave, but I tried and its not working, so
I was wondering if I could get some help.  If I can have it grabe the DNS
files from ns1, then I don't have to add the DNS entries to ns2 when I add
new ones to ns1.

			Adam

Which is worse:  Ignorance or Apathy?
Who Knows?  Who cares?
_____________________________________________________________
|Adam Williams                  adam@xxxxxxxxxx             |
|Network Administrator          Vicksburg Chemical Company  |
-------------------------------------------------------------

On Sun, 11 Jun 2000, Michael Zimmermann wrote:

> > Anyone have an idea on how to make a Raq3 do secondary DNS carching from a
> > primary DNS server on a Raq3i?
> 
> Well, to clarify the usage of words first: acting a) as a secondary and b)
> doing caching
> are two different things for me.
> 
> > I looked at /etc/named.conf on the raq3 and there is no line like:
> > zone "." {
> >   type hint;
> >   file "named.root";
> > };
> 
> Well then put it in, if it's not there (on my RaQ3 it was called DB.cache
> by the way). BUT the hint-file is ONLY for the root-servers; that has
> NOTHING to do with acting as a secondary.
> 
> So the first thing I would do is getting root and setting up named
> so that name-resolution is working on my RaQ.
> 
> Where to get the root-cache:
> -----------------------------
> 
> ;       This file is made available by InterNIC registration services
> ;       under anonymous FTP as
> ;           file                /domain/named.root
> ;           on server           FTP.RS.INTERNIC.NET
> ;       -OR- under Gopher at    RS.INTERNIC.NET
> ;           under menu          InterNIC Registration Services (NSI)
> ;              submenu          InterNIC Registration Archives
> ;           file                named.root
> 
> 
> 
> 
> Second thing - setting up named to act as a secondary:
> -------------------------------------------------------
> 
> Well, you have to be listed as one of the secondary servers,
> and the primary has to know you and respond to your
> axfr requests in a supportive manner (so to say :o).
> No well set-up server will do that - execpt if the requests
> come from somebody he knows to be his secondaries.
> 
> I don't think, that you are the secondary for intop.net.
> And being the secondary for 254.156.206.in-addr.arpa
> would mean that you had a whole bucket of IP-addresses
> delegated, which you have to register with RIPE or NIC
> or however you do that in your area.
> 
> So your problem seems to boil down to the first case only.
> Right?
> 
> 
> Greetings
> Michael
> 
> 
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>