Re: /etc/resolv.conf with 3 nameservers
[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 listed, one per keyword I've three DNS server in my /etc/resolv.conf in 6.0-REL: $ 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 whatever.domain.com') and if it does not know the addr, while the second one would know it, it does not resolve. Do I miss something? Thx matthias 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 were to disable the DNS server on 10.0.1.201, then it would use xxx.xxx.xxx.xxx or yyy.yyy.yyy.yyy to resolve the query. -- Ken Stevenson Allen-Myland Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf with 3 nameservers
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 were to disable the DNS server on 10.0.1.201, then it would use xxx.xxx.xxx.xxx or yyy.yyy.yyy.yyy to resolve the query. Yes, you're right. It is said in (...) that the fall down only works on timeout. I did not read carefully enough, stupid as I am. :-( matthias -- Matthias Apitz / Sisis Informationssysteme GmbH ein Tochterunternehmen der OCLC PICA B.V. Leiden (NL) D-82041 Oberhaching, Gruenwalder Weg 28g Fon: +49 89 / 61308-351, Fax: -399, Mobile +49 170 4527211 http://www.sisis.de/~guru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf with 3 nameservers
[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 different answer. If you were to disable the DNS server on 10.0.1.201, then it would use xxx.xxx.xxx.xxx or yyy.yyy.yyy.yyy to resolve the query. Yes, you're right. It is said in (...) that the fall down only works on timeout. I did not read carefully enough, stupid as I am. :-( 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 your local nameserver is authoritative for your local domain, then you probably want to know if it goes away, and those backups won't be able to look up names in your local domain. I'm making some assumptions about why you set things up this way in the first place, and I may be wrong, but there's too little info in your post to give definitive suggestions. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf with 3 nameservers
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 considered an answer to your query. It doesn't try another DNS server just to see if it gets a different answer. If you were to disable the DNS server on 10.0.1.201, then it would use xxx.xxx.xxx.xxx or yyy.yyy.yyy.yyy to resolve the query. Yes, you're right. It is said in (...) that the fall down only works on timeout. I did not read carefully enough, stupid as I am. :-( 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 your local nameserver is authoritative for your local domain, then you probably want to know if it goes away, and those backups won't be able to look up names in your local domain. I'm making some assumptions about why you set things up this way in the first place, and I may be wrong, but there's too little info in your post to give definitive suggestions. The anderlying problem is that we are three companies, now connected through VPN tunnels. Each company runs it's own DNS server internaly and without publicating all its names to Internet. The three DNS are 10.0.1.201 (mine one), xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy. Any idea? Yes, in the future we will unify the whole zone, but this is not a short term option... matthias -- Matthias Apitz / Sisis Informationssysteme GmbH ein Tochterunternehmen der OCLC PICA B.V. Leiden (NL) D-82041 Oberhaching, Gruenwalder Weg 28g Fon: +49 89 / 61308-351, Fax: -399, Mobile +49 170 4527211 http://www.sisis.de/~guru/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf with 3 nameservers
[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 your local nameserver is authoritative for your local domain, then you probably want to know if it goes away, and those backups won't be able to look up names in your local domain. I'm making some assumptions about why you set things up this way in the first place, and I may be wrong, but there's too little info in your post to give definitive suggestions. The anderlying problem is that we are three companies, now connected through VPN tunnels. Each company runs it's own DNS server internaly and without publicating all its names to Internet. The three DNS are 10.0.1.201 (mine one), xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy. Any idea? Yes, in the future we will unify the whole zone, but this is not a short term option... Presumably all three ranges have distinct domain names E.g. company1.de company2.de company3.de I am no expert of DNS, but isn't all you need for each company to run nameservers which are slaves (secondaries) for the other 2 as well as master of their own? So the nameserver at company1 is master for company1.de and is a slave for company2.de and company3.de etc. Of course, you might want some redundancy in that scenario, with each company running DNS on another server as well, and that one being a slave for all 3 domains. If you don't know enough to do that, I strongly recommend getting the latest edition of O'Reilly DNS and BIND; and you should find BIND doc on your FreeBSD system starting in /usr/share/doc/bind9/arm/Bv9ARM.html. Best, --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf with 3 nameservers
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 whatever.domain.com') and if it does not know the addr, while the second one would know it, it does not resolve. Do I miss something? If your nameserver at 10.whatever is returning NXDOMAIN, the resolver has gotten an answer and never asks for a second opinion from other nameservers. Fix your 10.whatever nameserver... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf and your ISP
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 http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf and your ISP
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 instance.
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.
Perhaps just a regular script that does a diff and patch of it, or
simply copies over the file you want regularly. Not elegant but it
would work.
According to dhclient.conf(5):
supersede [ option declaration ] ;
If for some option the client should always use a locally-configured
value or values rather than whatever is supplied by the server, these
values can be defined in the supersede statement.
I've never had to use this myself, but I would expect that something like:
interface foo {
...
supersede domain-name-servers 127.0.0.1;
...
}
would do the trick in your case.
-Glenn
I also wonder about creating a dhclient-exit script that would update
certain services automatically when your IP changes.
Thx.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf and your ISP
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 domain-name-servers 127.0.0.1;
...
}
would do the trick in your case.
See also the prepend option.
(I use supersede to keep my own domain, and Prepend to make
sure my DNS server is first on the list.)
Robert Huff
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /etc/resolv.conf
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 had earlier. I just don't find the script/program which rewrites it. Can somebody please help me ...thanks in advance To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: /etc/resolv.conf
# [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 list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: /etc/resolv.conf
-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 please help me man dhclient-script thanks in advance To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
