Re: How to force a static /etc/resolv.conf?
On 13/06/2013 02:46, Darren Pilgrim wrote: I'm running 9.1. I run a local recursive resolver, so my /etc/resolv.conf needs to remain static. I have DHCPv4, DHCPv6 and VPN clients running which all want to modify /etc/resolv.conf. I have set in /etc/resolvconf.conf: search_domains=example.com. example.net. name_servers=2001:db8::53 But that only prepends that information. Search domains and nameservers from other sources still get included. I can set /etc/resolv.conf as immutable, but's a hack and it generates errors from resolveconf. How do I tell resolvconf to always use a static configuration or, better yet, to not muck with /etc/resolv.conf at all? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Hi, You can configure it in your dhclient.conf file. Use the supersede keyword. For example, in your case add: supersede domain-search example.com example.net supersede domain-name-servers 2001:db8::53 to your /etc/dhclient.conf Loic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to force a static /etc/resolv.conf?
On 2013-06-13 05:02, Loic Capdeville wrote: You can configure it in your dhclient.conf file. Use the supersede keyword. For example, in your case add: supersede domain-search example.com example.net supersede domain-name-servers 2001:db8::53 That only addresses the DHCPv4 client. The DHCPv6 client doesn't have those options and neither do the VPN clients. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to force a static /etc/resolv.conf?
On 2013-06-12 17:46, Darren Pilgrim wrote: How do I tell resolvconf to always use a static configuration or, better yet, to not muck with /etc/resolv.conf at all? According to the project developer, the answer is to have resolvconf not touch /etc/resolv.conf by put the following in /etc/resolvconf.conf resolv_conf=/dev/null Then you just edit /etc/resolv.conf directly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to force a static /etc/resolv.conf?
I'm running 9.1. I run a local recursive resolver, so my /etc/resolv.conf needs to remain static. I have DHCPv4, DHCPv6 and VPN clients running which all want to modify /etc/resolv.conf. I have set in /etc/resolvconf.conf: search_domains=example.com. example.net. name_servers=2001:db8::53 But that only prepends that information. Search domains and nameservers from other sources still get included. I can set /etc/resolv.conf as immutable, but's a hack and it generates errors from resolveconf. How do I tell resolvconf to always use a static configuration or, better yet, to not muck with /etc/resolv.conf at all? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
resolvconf overwriting /etc/resolv.conf
Hi, I run bind on a LAN, with some LAN-only (sub)domains. On the LAN is also a DSL modem/router that advertises ipv6 addresses. So far so good. However, since I upgraded the server from 8-STABLE to 9.1-PRERELEASE, the /etc/resolv.conf gets overwritten by the resolvconf script, with an ipv6 nameserver (presumably the router, haven't checked). This is not what I want. Now I see that you can prepend nameservers through /etc/resolvconf.conf, but what I really want is for resolvconf to leave my /etc/resolv.conf alone. Is there any way to disable the script (apart from deleting it)? thanks, Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
sendmail /etc/resolv.conf modified by DHCP
Hello, At home I have my WLAN as 192.168.2.0/24. After moving to my office and rebooting there, I encounter that sendmail receives messages (via fetchmail) terrible slow. I digged into this and see that the sendmail issues wrong DNS requests as (for example): 08:51:18.753491 IP xx.xx.xx.xx.49812 192.168.2.1.53: 12793+ MX? ubuntu.com.Sisis.de. (37) 08:51:18.867365 IP xx.xx.xx.xx.42619 192.168.2.1.53: 12793+ MX? physik.uni-wuerzburg.de.Sisis.de. (50) 08:51:18.982491 IP xx.xx.xx.xx.52554 192.168.2.1.53: 12794+ ? lexasoft.ru. (29) 08:51:19.095490 IP xx.xx.xx.xx.10093 192.168.2.1.53: 12794+ ? des.no. (24) The reason is obvious: - the /etc/resolv.conf on shutdown at home has this DNS resolver; - in my office the system comes up and when at some point the WLAN interface associates, it gets an IP and a new /etc/resolv.conf file; Why sendmail does not honour the new /etc/resolv.conf and stays with the old DNS server IP? How this is supposed to fix? An idea would be to restart sendmail via a devd hook, but maybe there is some config values for sendmail that it always check /etc/resolv.conf for fresh? Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ¡Ya basta! ¡Tropas de OTAN, fuera de Afghanistan! There's an end of it! NATO troups out of Afghanistan! Schluss jetzt endlich! NATO raus aus Afghanistan! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How did the /etc/resolv.conf appear?
The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? Are these entries created during installation? Elisey Babenko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How did the /etc/resolv.conf appear?
[EMAIL PROTECTED] wrote: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? Are these entries created during installation? Elisey Babenko ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] do you use DHCP? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How did the /etc/resolv.conf appear?
--- [EMAIL PROTECTED] wrote: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? Are these entries created during installation? They were probably put there by your internet access mechanism (PPP / PPPOE). Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How did the /etc/resolv.conf appear?
In the last episode (Dec 17), [EMAIL PROTECTED] said: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? Are these entries created during installation? They could have been, if you selected DHCP configuration. In addition to your IP address, the server can also hand out DNS server addresses, which dhcpd will use to create a resolv.conf file. -- Dan Nelson [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: How did the /etc/resolv.conf appear?
On Dec 17, 2006, at 12:17 PM, [EMAIL PROTECTED] wrote: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? Are these entries created during installation? You must be using DHCP to obtain an address for your network interface (s)... -jav ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How did the /etc/resolv.conf appear?
[EMAIL PROTECTED] writes: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? Are these entries created during installation? Are you running DHCP(-client)? If so, consider the prepend and supercede directives. 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: How did the /etc/resolv.conf appear?
[EMAIL PROTECTED] wrote: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? The entries are created by dhclient or whichever different program establishes the connection, when it receives the necessary information (your IP, gateway and the nameservers to use) from your ISP. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How did the /etc/resolv.conf appear?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? Are these entries created during installation? Elisey Babenko By default dhcpcd does this. - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFhZFTEnKyINQw/HARAuXQAKCONJaEPSalX0X/U9/4EZ05oq6hAACfU05j j0F7JiZYCXBKijnRiY1Q9gU= =FfRr -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How did the /etc/resolv.conf appear?
On Sun, Dec 17, 2006 at 06:42:46PM +0100, [LoN]Kamikaze wrote: [EMAIL PROTECTED] wrote: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? The entries are created by dhclient or whichever different program establishes the connection, when it receives the necessary information (your IP, gateway and the nameservers to use) from your ISP. I do not use any special DHCP client, but I use mpd(8) to connect via ADSL. I thought, mpd has created these entries. But when I temporary moved resolv.conf and restarted the computer, no resolv.conf appeared. So I steel don't know, who created resolv.conf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How did the /etc/resolv.conf appear?
On Sun, Dec 17, 2006 at 06:42:46PM +0100, [LoN]Kamikaze wrote: [EMAIL PROTECTED] wrote: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? The entries are created by dhclient or whichever different program establishes the connection, when it receives the necessary information (your IP, gateway and the nameservers to use) from your ISP. I do not use any special DHCP client, but I use mpd(8) to connect via ADSL. I thought, mpd has created these entries. But when I temporary moved resolv.conf and restarted the computer, no resolv.conf appeared. So I steel don't know, who created resolv.conf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How did the /etc/resolv.conf appear?
On Sun, Dec 17, 2006 at 06:42:46PM +0100, [LoN]Kamikaze wrote: [EMAIL PROTECTED] wrote: The automatically installed /etc/resolv.conf contains the next: nameserver 82.207.67.2 nameserver 213.179.244.18 Today I discovered that this servers is not servers of FreeBSD.org or InterNIC, but of my ISP. I wonder how the system found these IP addresses? The entries are created by dhclient or whichever different program establishes the connection, when it receives the necessary information (your IP, gateway and the nameservers to use) from your ISP. I do not use any special DHCP client, but I use mpd(8) to connect via ADSL. I thought, mpd has created these entries. But when I temporary moved resolv.conf and restarted the computer, no resolv.conf appeared. So I steel don't know, who created resolv.conf. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/etc/resolv.conf with 3 nameservers
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 -- 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: 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]
/etc/resolv.conf and your ISP
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. 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]
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: options in /etc/resolv.conf
On Mon, 10 May 2004, Matthew Seaman wrote: FreeBSD uses a pretty standard version of BIND-8.3.7, and it uses the BIND resolver code in libc -- See: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libbind/Makefile?rev=1.7content-type=text/x-cvsweb-markup The part you're interested in is handled by the code in res_init.c: look for the res_setoptions() function in: http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/bind/lib/resolv/res_init.c?rev=1.1.1.8content-type=text/x-cvsweb-markup Which suggests that the functionality you require is available, and that the man page is somewhat lacking. Note that the man page isn't supplied with the BIND sources, so it may well have got out of synch. Have you tried using those options in your /etc/resolv.conf? Do they work? I have tried the options. options timeout:60 I added it to /etc/resolv.conf However, it doesnt seem to work, because the timeout period is still 40 seconds. Weird enough are nowhere errors detectable that the options isnt possible or anything. Bye, Reinoud. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: options in /etc/resolv.conf
On Mon, May 10, 2004 at 01:53:01PM +0200, Mipam wrote: I wish to use the following option in /etc/resolv.conf options timeout:40 However in man resolv.conf(5) i notice that this option isnt available. But i read here: http://ops.ietf.org/lists/namedroppers/namedroppers.199x/msg03798.html that this option is available from bind 8.2 named -v yields: named 8.3.7-REL Does freebsd use a modified version with not all options which comes in bind 8.3? FreeBSD uses a pretty standard version of BIND-8.3.7, and it uses the BIND resolver code in libc -- See: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libbind/Makefile?rev=1.7content-type=text/x-cvsweb-markup The part you're interested in is handled by the code in res_init.c: look for the res_setoptions() function in: http://www.freebsd.org/cgi/cvsweb.cgi/src/contrib/bind/lib/resolv/res_init.c?rev=1.1.1.8content-type=text/x-cvsweb-markup Which suggests that the functionality you require is available, and that the man page is somewhat lacking. Note that the man page isn't supplied with the BIND sources, so it may well have got out of synch. Have you tried using those options in your /etc/resolv.conf? Do they work? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
options in /etc/resolv.conf
Hi, I wish to use the following option in /etc/resolv.conf options timeout:40 However in man resolv.conf(5) i notice that this option isnt available. But i read here: http://ops.ietf.org/lists/namedroppers/namedroppers.199x/msg03798.html that this option is available from bind 8.2 named -v yields: named 8.3.7-REL Does freebsd use a modified version with not all options which comes in bind 8.3? Bye, Mipam. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SQUID ignores /etc/resolv.conf
Hi fellows, Is it possible that SQUID doesn't care about nameservers listed in /etc/resolv.conf ? We experienced the following effect: in /etc/resolv.conf it says nameserver a.b.c.d a.b.c.e When 'a.b.c.d' went down SQUID couldn't do dns lookups anymore, while the machine itself could. Adding the following to squid.conf: dns_nameserver a.b.c.d a.b.c.e with 'a.b.c.d' still down produced a delay of about three seconds and a successful lookup/download. It seems as if SQUID didn't fall back to the second nameserver as long it's only listed in /etc/resolf.conf. Does anyone experience the same? Mit freundlichen Gruessen / with kind regards +++ S t e p h a n F. Y a r a g h c h i +++ +++ Information Technology +++ +++ Boerse Berlin-Bremen +++ Fasanenstr. 85 +++ 10623 Berlin +++ +++ mail [EMAIL PROTECTED] +++ web http://www.boerse-berlin-bremen.de +++ +++ phone +49 (0) 30 3110910 +++ fax +49 (0) 30 31109178 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SQUID ignores /etc/resolv.conf
In the last episode (Apr 06), Yaraghchi, Stephan said: Is it possible that SQUID doesn't care about nameservers listed in /etc/resolv.conf ? We experienced the following effect: in /etc/resolv.conf it says nameserver a.b.c.d a.b.c.e Try: nameserver a.b.c.d nameserver a.b.c.e instead and see if that works. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: SQUID ignores /etc/resolv.conf
-Original Message- From: Dan Nelson [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 4:24 PM To: Yaraghchi, Stephan Cc: [EMAIL PROTECTED] Subject: Re: SQUID ignores /etc/resolv.conf In the last episode (Apr 06), Yaraghchi, Stephan said: Is it possible that SQUID doesn't care about nameservers listed in /etc/resolv.conf ? We experienced the following effect: in /etc/resolv.conf it says nameserver a.b.c.d a.b.c.e Try: nameserver a.b.c.d nameserver a.b.c.e instead and see if that works. -- Dan Nelson [EMAIL PROTECTED] Thank you, Dan. You hit the right spot. I was a bit hesitant since the systems are in production, but your guess was correct. I crosschecked the handbook and found your notation there as well. Don't know what made me put them on one line... Greetings from Berlin, Stephan. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/etc/resolv.conf
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
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
Cant find /etc/resolv.conf
Hello there... I've the last version of freebsd... But i cant find the file /etc/resolv.conf Why? Tiago Camilo _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Cant find /etc/resolv.conf
Today Tiago Andre wrote: Hello there... I've the last version of freebsd... But i cant find the file /etc/resolv.conf Why? Why??? Who knows? Maybe it's simply not there. But you can create one if you have write access to the /etc dir. It's nothing special with this file, i.e: nameserver xxx.xxx.xxx.xxx nameserver xxx.xxx.xxx.xxx nameserver xxx.xxx.xxx.xxx domain x.tld # - or - search x.tld See resolv.conf(5) for more. -andrew Tiago Camilo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Cant find /etc/resolv.conf
On Thu, 2002-12-05 at 13:42, Tiago Andre wrote: Hello there... I've the last version of freebsd... But i cant find the file /etc/resolv.conf Why? The answer is: you didn't configure your networking via sysinstall. There is no default /etc/resolv.conf in FreeBSD distributions. It's created automatically when you go to configure/networking/interfaces menu in sysinstall (and couple of other cases). Tiago Camilo _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message Regards, Sergey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: dhcp option to *not* overwrite /etc/resolv.conf
Hi,
I have read the man pages, searched a few forums, but I did not found a
way to prevent dhcp to do not change my /etc/resolv.conf. I do not have
You can write a script to fix resolv.conf right after dhclient ruined
it. The way to do it is to hook it from /etc/dhclient-exit-hooks
(which you'll need to create). Here's mine, which calls two other scripts (not
included), one of which only if the IP address actually changed. This one
also gets the new servers as arguments.
-- /etc/dhclient-exit-hooks
# nothing to do unless we're bound
case ${reason} in
BOUND | RENEW | REBIND | REBOOT )
[ -x /etc/set-ntp ] . /etc/set-ntp
if [ -n ${new_domain_name_servers} ]; then
if [ -z ${old_domain_name_servers} ] || [ x${old_ip_address} !=
x{$new_ip_address} ]; then
[ -x /etc/refresh-named ] /etc/refresh-named
${new_domain_name_servers}
fi
fi
;;
esac
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
dhcp option to *not* overwrite /etc/resolv.conf
Hi, I have read the man pages, searched a few forums, but I did not found a way to prevent dhcp to do not change my /etc/resolv.conf. I do not have access to the dhcp server configuration, so I need to change it on my client. I also tried to chmod it to only read mode, but that did not work out. Any tips? thanks Paulo __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: dhcp option to *not* overwrite /etc/resolv.conf
Never tried it, but you could look for the spot in the various rc* files that setup dhcp and once it's done re-write /etc/resolv.conf with what you want it to be... ? On Mon, 28 Oct 2002, Paulo Roberto wrote: Hi, I have read the man pages, searched a few forums, but I did not found a way to prevent dhcp to do not change my /etc/resolv.conf. I do not have access to the dhcp server configuration, so I need to change it on my client. I also tried to chmod it to only read mode, but that did not work out. Any tips? thanks Paulo __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/ 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: Re: dhcp option to *not* overwrite /etc/resolv.conf
I have read the man pages, searched a few forums, but I did not found a way to prevent dhcp to do not change my /etc/resolv.conf. I do not have access to the dhcp server configuration, so I need to change it on my client. I also tried to chmod it to only read mode, but that did not work out. Any tips? Depending what it is you want to not be overwritten you should be able to achieve the desired results throught supersede and/or prepend statements in dhcp.conf. OpenBSD supports use of a resolv.conf.tail file that also hold entries you don't want overwritten (no idea about FreeBSD). Work like you don't need the money Dance like nobody's watching Love like you've never been hurt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: dhcp option to *not* overwrite /etc/resolv.conf
On Mon, Oct 28, 2002 at 02:11:48PM -0800, Paulo Roberto wrote:
Hi,
I have read the man pages, searched a few forums, but I did not found a
way to prevent dhcp to do not change my /etc/resolv.conf. I do not have
access to the dhcp server configuration, so I need to change it on my
client. I also tried to chmod it to only read mode, but that did not
work out. Any tips?
man dhclient.conf
As an example my /etc/dhclient.conf contains the following:
interface ed0 {
supersede domain-name-servers 127.0.0.1;
append domain-name example.com;
}
The resulting /etc/resolv.conf looks like this:
search isp.domain.com example.com
nameserver 127.0.0.1
--
Robin Damm [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: dhcp option to *not* overwrite /etc/resolv.conf
add this to your /etc/dhclient.conf
interface (outside interface) {
supersede domain-name-servers (preferred DNS);
}
you can alternately use prepend domain-name-servers to add your DNS to the
TOP of the resolv.conf list.
- Original Message -
From: Paulo Roberto [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, October 28, 2002 5:11 PM
Subject: dhcp option to *not* overwrite /etc/resolv.conf
Hi,
I have read the man pages, searched a few forums, but I did not found a
way to prevent dhcp to do not change my /etc/resolv.conf. I do not have
access to the dhcp server configuration, so I need to change it on my
client. I also tried to chmod it to only read mode, but that did not
work out. Any tips?
thanks
Paulo
__
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/
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
