Hi,
The man page of resolv.conf claims:
The different configuration options are:
nameserver Internet address (in dot notation) of a name server that the
resolver should query. Up to MAXNS (currently 3) name
servers may be listed, one per
[EMAIL PROTECTED] wrote:
Hi,
The man page of resolv.conf claims:
The different configuration options are:
nameserver Internet address (in dot notation) of a name server that the
resolver should query. Up to MAXNS (currently 3) name
servers may be
El día Monday, April 10, 2006 a las 10:44:52AM -0400, Ken Stevenson escribió:
I think the problem is that once your first server responds with a
domain not found, that's considered an answer to your query. It
doesn't try another DNS server just to see if it gets a different
answer. If you
[EMAIL PROTECTED] wrote:
El día Monday, April 10, 2006 a las 10:44:52AM -0400, Ken Stevenson escribió:
I think the problem is that once your first server responds with a
domain not found, that's considered an answer to your query. It
doesn't try another DNS server just to see if it gets a
El día Monday, April 10, 2006 a las 04:07:34PM +0100, Alex Zbyslaw escribió:
[EMAIL PROTECTED] wrote:
El día Monday, April 10, 2006 a las 10:44:52AM -0400, Ken Stevenson
escribió:
I think the problem is that once your first server responds with a
domain not found, that's
[EMAIL PROTECTED] wrote:
El día Monday, April 10, 2006 a las 04:07:34PM +0100, Alex Zbyslaw escribió:
There's nothing to stop you configuring that local nameserver to use
your two backups for names that it cannot resolve.
You could then leave the two backups in /etc/resolv.conf but if
On Apr 10, 2006, at 9:54 AM, [EMAIL PROTECTED] wrote:
$ cat /etc/resolv.conf
domain Sisis.de
nameserver 10.0.1.201
nameserver xxx.xxx.xxx.xxx
nameserver yyy.yyy.yyy.yyy
But only the 1st one (10.0.1.201) is contacted to make the name lookup
(I've checked this with trussing a 'ping
