>From your crontab, simply do a dig @rs.internet.net each week.
That should do a quick and dirty update of your root.cache fairly
easily without work.
Maintaining a caching name server is pretty simple stuff.
On Wed, 30 Sep 1998, Siu, Andy wrote:
> Date: Wed, 30 Sep 1998 14:45:00 +1000
> From: "Siu, Andy" <ASiu@vnpbnes1.telstra.com.au>
> To: Glenn Graham <glenn@intextonline.com>
> Cc: "Mailing List, Linux Networking" <linux-net@vger.rutgers.edu>
> Subject: Re: DNS: Can't find server & forwarders not working
>
>
> Yes, I agree your suggestion will probably work, though I have not tried it.
> But I forgot to mention that I deliberately cleared up my cache file so
> there is no hint where the root name servers are. The reason is that I did
> not want to maintain it.
>
> I may have to do it if that is the only way. I still like to understand why
> the system behaved the way it did.(the itch still has not gone away).
>
> Cheers
> Andy
> ----------
> From: Glenn Graham
> To: Siu, Andy
> Cc: Mailing List, Linux Networking
> Subject: Re: DNS: Can't find server & forwarders not working
> Date: Wednesday, 30 September 1998 10:15AM
>
>
>
> /etc/resolv.conf is your magic file.
>
> Anything you place there, will be used to do the lookups.
>
> If your box is linux, you might consider configuring a simple
> caching nameserver, you can run locally that will be much faster
> and more reliable, then using your isp's
>
> Do this:
> ( Configuration for BIND4 / Dig2.2 - Can't recall for BIND-8 )
>
> mkdir /var/named
> dig @rs.internic.net > /var/named/root.cache.
>
> Then creat an /etc/named.boot file like so;
>
> ;
> ; boot file for name server
> ;
> directory /var/named
> ;
> ; type domain source host/file backup file
> ;
> cache . root.cache
>
> Then rehup /usr/sbin/named ;
> ps -ax look for the named demon, the kill -HUP pid#
>
>
> The in /etc/resolv.conf
>
> nameserver 0.0.0.0 ( or nameserver localhost ) ( or 127.0.0.1 )
>
>
> ===================================================================
>
> There you now have your very own local caching nameserver.
>
>
>
> On Wed, 30 Sep 1998, Siu, Andy wrote:
>
> > Date: Wed, 30 Sep 1998 09:52:00 +1000
> > From: "Siu, Andy" <ASiu@vnpbnes1.telstra.com.au>
> > To: "Mailing List, Linux Networking" <linux-net@vger.rutgers.edu>
> > Subject: DNS: Can't find server & forwarders not working
> >
> > Dear fellow linux experts and users,
> >
> > I have set up my own DNS server for resolving names in my private domain
> > (192.168.168.xxx). Also I want to use service of the name servers
> suggested
> > by my ISP to resolve names on the internet. (I have set up the PPP and it
> > seems to be working ok.) I tried two things, both unsuccessful.
> > 1. I put the suggested name server address in resolv.conf
> >
> > Content of my resolv.conf is:
> >
> >
>
> ----------------------------------------------------------------------------
> > --------------------------------------
> > nameserver 203.17.73.5
> > nameserver 203.17.73.6
> > nameserver 127.0.01
> >
> >
>
> ----------------------------------------------------------------------------
> > --------------------------------------
> >
> > Starting nslookup, it says:
> >
> >
>
> ----------------------------------------------------------------------------
> > --------------------------------------
> > ***Can't find server name for address 203.17.73.5 : Non-existent
> > host/domain
> > ***Can't find server name for address 203.17.73.6 : Non-existent
> > host/domain
> > Default server : local host
> > Address : 127.0.0.1
> > >
> >
> >
>
> ----------------------------------------------------------------------------
> > --------------------------------------
> >
> > However when I queried the name server 203.17.73.5 directly in nslookup,
> it
> > works fine. I did this by changing the server in nslookup and then ask it
> > to resolve sunsite.unc.edu:
> >
> >
>
> ----------------------------------------------------------------------------
> > --------------------------------------
> > >server 203.17.73.6
> > Default server : xxxxxxxxxxxxxxx [can't remember the exact response here]
> > Address : 203.17.73.6
> > >sunsite.unc.edu
> > [proper answer then returned from the name server]
> >
> >
>
> ----------------------------------------------------------------------------
> > --------------------------------------
> >
> > Is there something wrong with the suggested name servers or is it my set
> up?
> >
> > 2. I added the "forwarders" line to the local name server with the two
> name
> > server addresses provided by the ISP.
> >
> > Since nslookup cannot use the suggest server as default, I tried to use my
> > local named to forward my request to them. However, nslookup failed to
> > resolve names like sunsite.unc.edu. It said something like "non-existent
> > host/domain" (from memory, can't repeat the exact wording).
> >
> > Again is it that the server failed to perform recursive name resolution or
> > is it my set up.
> >
> > Also any suggestion of other ways to achieve my primary objective.
> >
> > Thanks for any help.
> >
> > Regards
> > Andy Siu
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-net" in
> > the body of a message to majordomo@vger.rutgers.edu
> >
>
>
>
> **********************************************
> inTEXT Communications Vancouver BC Canada
> Corporate Intranet & Internet Security
> System Administration - FireWall Systems
> Linux Bsd FreeBSD Programming Perl / c / c++
> www.intextonline.com | glenn@intextonline.com
>
**********************************************
inTEXT Communications Vancouver BC Canada
Corporate Intranet & Internet Security
System Administration - FireWall Systems
Linux Bsd FreeBSD Programming Perl / c / c++
www.intextonline.com | glenn@intextonline.com
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu