On Sat, 19 Aug 2000 19:49:05 +0100, "Bruce Phipps"
>>It doesn't store anything to the
>harddrive, so at each reboot, or restart of named it will lose it's
>information and you'll have to rebuild the cache.<
>So, its no good for me to run a caching nameserver on a laptop, then?
Not if you shut it down frequently, no. I mean, it won't cause any
harm, but it won't really help you much, either.
Quote:>Every time I reboot, I have to rebuild DNS lookup information from scratch.
>Looks like I have run into an issue caused by running a server OS which
>should be on 24x7 on a laptop computer?
Well, Linux is very well suited for many applications besides serving.
It makes a great workstation for developing, graphics, sound, etc.
About the only thing it doesn't do very well is games, really. And
we're starting to charge ahead in that finally.
Back to your DNS problem, though. Is your laptop your only sytem? If
you have access to even an old 486 (Although you have to watch this.
I have a 486DX that won't dial up because the UART is incompatible)
then you could use that for a dialup router. Then leave it on all the
time running ipchains, bind, and diald (optional) and hook your laptop
to it. I wonder sometimes about diald. Personally I never got it to
work, and besides who wants to wait for the system to dial up when you
could already be up and running? I have an AMD 200 that I'm using for
a gateway system, amoung other things, that is on a 56k dial up
connection and I just wrote a keep alive script for it. I average 5
days or so uptime before I get disconnected, then just reconnect and
I'm good for another 5 days :) The system also runs Bind as a
cahching nameserver and squid to cache objects. Frequently viewed
sites are up almost before you enter the URL. ;-)
Quote:>Bruce
-----
After many hours of trying and praying (I converted to 7 different religions over the course of an hour. None of them had Linux tech support)
--Dru Lee Parsec from a post made on linuxnewbie.org message boards
by