[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
Also of note... if you change the bits on the file to nochg, so it can't
be updated, Comcast will detect this and disable your connection (it
happened to me).
___
freebsd-questions@freebsd.org mailing list
At 12:49 PM 5/8/2005, Forrest Aldrich wrote:
I can think of a few ways to resolve this, but I thought to ask here.
I have Comcast for my ISP, and of course DHCP changes /etc/resolv.conf
during each update -- lately, they've been screwing things up bigtime,
such that I simply use my own named
Glenn Dawson writes:
My question is: how to reliably keep your own nameserver in
/etc/resolv.conf, and get around the frequent protocol updates that
change/nullify your mods to /etc/resolv.conf.
According to dhclient.conf(5):
interface foo {
...
supersede
Check out
dhclient
which uses the dhclient-script to overwrite your resolv.conf under certain
(such as the default) conditions.
Dw.
On Thu, 2 Jan 2003, McClain wrote:
Hello ppl,
i got a problem with /etc/resolv.conf. On every start up, it gets
somehow overwritten with settings i
# [EMAIL PROTECTED] / 2003-01-02 14:47:57 +:
i got a problem with /etc/resolv.conf. On every start up, it gets
somehow overwritten with settings i had earlier. I just don't find
the script/program which rewrites it. Can somebody please help me
DHCP?
--
If you cc me or remove the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of McClain
i got a problem with /etc/resolv.conf. On every start up, it gets
somehow overwritten with settings i had earlier. I just don't find
the script/program which rewrites it. Can somebody
12 matches
Mail list logo
