hanche@imf.unit.no (Harald Hanche-Olsen) (02/19/91)
In article <4fe14e43.1bc5b@pisa.ifs.umich.edu> rees@pisa.ifs.umich.edu (Jim Rees) writes:
Uncomment the 'nmconfig' lines in /etc/rc.local. Create the empty file
/etc/daemons/nmconfig. Create the file /etc/resolv.conf. It should look
like this:
domain domain-name
nameserver server1
nameserver server2
nameserver server3
where domain-name is your domain name, and server1..n are the numeric IP
addresses of your name servers. You can have as many as you want, it tries
them in the order listed.
That's what the manual says. Last time our primary name server became
unavailable, our machines would not revert to the second one and so
most addresses were rejected as `unknown'. Yes I did check that the
second name server was up and responsive. Guess I should have APR'd
it, but then I snowed under in other chores and the primary name
server has never been off-line since...
- Harald Hanche-Olsen <hanche@imf.unit.no>
Division of Mathematical Sciences
The Norwegian Institute of Technology
N-7034 Trondheim, NORWAYjf@ap.co.umist.ac.uk (John Forrest) (02/20/91)
In article <HANCHE.91Feb18195355@hufsa.imf.unit.no> hanche@imf.unit.no (Harald Hanche-Olsen) writes: >In article <4fe14e43.1bc5b@pisa.ifs.umich.edu> rees@pisa.ifs.umich.edu (Jim Rees) writes: > > Uncomment the 'nmconfig' lines in /etc/rc.local. Create the empty file > /etc/daemons/nmconfig. Create the file /etc/resolv.conf. It should look > like this: > > domain domain-name > nameserver server1 > nameserver server2 > nameserver server3 > > where domain-name is your domain name, and server1..n are the numeric IP > addresses of your name servers. You can have as many as you want, it tries > them in the order listed. > >That's what the manual says. Last time our primary name server became >unavailable, our machines would not revert to the second one and so >most addresses were rejected as `unknown'. Yes I did check that the >second name server was up and responsive. Guess I should have APR'd >it, but then I snowed under in other chores and the primary name >server has never been off-line since... > >- Harald Hanche-Olsen <hanche@imf.unit.no> > Division of Mathematical Sciences > The Norwegian Institute of Technology > N-7034 Trondheim, NORWAY We are running a non-standard system in this area. We run OS10.1, but have added BIND4.6 by the expedient of removing the entries from the main clib (or is it libc?) library, and adding our own resolvlib. We still basically get this problem though, and I have never solved it. Basically there is a 30s timeour (or so), so if the server is down you wait 30s (or something like that) before it tries the next server in this list. However, our primary servers are rarely down either - but it does speed things up to put in actual numbers in the powerup /etc/ifconfig's! John Forrest Dept of Computation UMIST
rees@pisa.ifs.umich.edu (Jim Rees) (02/20/91)
In article <HANCHE.91Feb18195355@hufsa.imf.unit.no>, hanche@imf.unit.no (Harald Hanche-Olsen) writes:
You can have as many as you want, it tries
them in the order listed.
That's what the manual says. Last time our primary name server became
unavailable, our machines would not revert to the second one and so
most addresses were rejected as `unknown'.
This works for me, with sr10.3, at least some of the time. Maybe it depends
on the error you get back, whether it's timeout or refused or whatever.