Re: resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
Hi,
On Mon, 8 Aug 2011 07:55:11 -0400
J.R. Oldroyd f...@opal.com said:
Is there any chance that you could create a patch for 8.2 based on the
commits in HEAD?
That would be great!
fbsd Better would be to ask hrs@ to MFC his commits to 8-stable.
hrs@ posted MFC candidate patch for review. Please refer the thread
started from:
http://lists.freebsd.org/pipermail/freebsd-net/2011-June/029070.html
The patches you will find in the thread are:
http://people.freebsd.org/~hrs/rfc6106_stable8_20110612-1.diff
http://people.freebsd.org/~ume/resolvconf-releng_8.diff
You may be interested in the thread from the following as well:
http://lists.freebsd.org/pipermail/freebsd-net/2011-June/029091.html
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
Hi,
On Mon, 08 Aug 2011 16:42:06 +1000
Mattia Rossi mro...@swin.edu.au said:
mrossi Anyhow, the manpage is really not clear about name_servers_append, and
mrossi it's not working as expected either:
mrossi 1) If I put in a comma separated list of nameservers, I'll find that
mrossi comma separated list in /etc/resolv.conf under a single nameserver
mrossi tag. That doesn't work, as it's not a valid entry. Each nameserver
mrossi needs to have a nameserver host entry.
name_servers and name_servers_append is a space separated list of
nameserver.
mrossi 2) If I use multiple name_servers_append entries in
mrossi /etc/resolvconf.conf, then only the last entry is used. I don't want
mrossi only one DNS server there though, I want all three of them, as I
mrossi already had the problem that one or the other didn't work properly.
You can specify multiple nameservers in name_servers and/or
name_servers_append.
mrossi 3) If I read the description for name_servers in resolvconf.conf(5), I
mrossi understand that this tag prepends the nameserver to my list. This is
mrossi not what happens. Still not sure what actually happens there...
It is strange to me. If you specify name_servers, it should be
prepended to the nameserver list. I've just tried name_servers, and
it did the job as expected, here.
mrossi How do I get my 3 manual DNS entries properly into my resolv.conf ?
Please specify your 3 servers as space separated list in name_servers
or name_servers_append.
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
On 10/08/2011 17:29, Hajimu UMEMOTO wrote: Hi, On Mon, 08 Aug 2011 16:42:06 +1000 Mattia Rossimro...@swin.edu.au said: mrossi Anyhow, the manpage is really not clear about name_servers_append, and mrossi it's not working as expected either: mrossi 1) If I put in a comma separated list of nameservers, I'll find that mrossi comma separated list in /etc/resolv.conf under a single nameserver mrossi tag. That doesn't work, as it's not a valid entry. Each nameserver mrossi needs to have a nameserverhost entry. name_servers and name_servers_append is a space separated list of nameserver. Ahh, okay, that works. Might be worth mentioning in the manpage though. Maybe an example wouldn't be too bad either mrossi 2) If I use multiple name_servers_append entries in mrossi /etc/resolvconf.conf, then only the last entry is used. I don't want mrossi only one DNS server there though, I want all three of them, as I mrossi already had the problem that one or the other didn't work properly. You can specify multiple nameservers in name_servers and/or name_servers_append. Of course, once 1) is solved 2) is redundant. mrossi 3) If I read the description for name_servers in resolvconf.conf(5), I mrossi understand that this tag prepends the nameserver to my list. This is mrossi not what happens. Still not sure what actually happens there... It is strange to me. If you specify name_servers, it should be prepended to the nameserver list. I've just tried name_servers, and it did the job as expected, here. Hmm, not sure what happened last time here, but I've tried it now with a single nameserver, a space separated list of nameservers and a mix of name_servers and name_servers_append entries and it worked perfectly. It also eliminated duplicate entries in name_servers and name_servers_append, preferring the one in name_servers. Again, maybe worthwhile mentioning in the manpage. mrossi How do I get my 3 manual DNS entries properly into my resolv.conf ? Please specify your 3 servers as space separated list in name_servers or name_servers_append. Yes, got it. All good! Thanks to all! Mat ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
On 05/08/2011 16:52, Doug Barton wrote: On 08/04/2011 22:59, Mattia Rossi wrote: Hi all, I've finally patched my 8.2 IPv6 gateway with the RDNSS/DNSSL patches and I'm distributing DNS servers that way now. Works fine, my box running CURRENT picks up the DNS servers and search domains and writes them into /etc/resolv.conf using the resolvconf script. The script anyhow overwrites my previous manual entries in /etc/resolv.conf which I need for my manual IPv4 setup... I think it's an easily fixable bug - haven't looked into it that close atm., but given that the resolvconf script is going to be rewritten/enhanced anyways, that's something to keep in mind. I think that manual entries should always be preferred. Check 'man resolvconf.conf' for information on name_servers_append. It would probably be nice if there was a _prepend equivalent. Okay, finally got around to read that manpage (which I didn't realise that it existed). So For RDNSS/DNSSL we have now the following manpages related to resolv.conf: resolvconf(8), resolv.conf(5) (aka. resolver(5)) and resolvconf.conf(5)... Lot's of resolvconfs :-) Anyhow, the manpage is really not clear about name_servers_append, and it's not working as expected either: 1) If I put in a comma separated list of nameservers, I'll find that comma separated list in /etc/resolv.conf under a single nameserver tag. That doesn't work, as it's not a valid entry. Each nameserver needs to have a nameserver host entry. 2) If I use multiple name_servers_append entries in /etc/resolvconf.conf, then only the last entry is used. I don't want only one DNS server there though, I want all three of them, as I already had the problem that one or the other didn't work properly. 3) If I read the description for name_servers in resolvconf.conf(5), I understand that this tag prepends the nameserver to my list. This is not what happens. Still not sure what actually happens there... How do I get my 3 manual DNS entries properly into my resolv.conf ? Mat ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
On Mon, 08 Aug 2011 10:46:16 +1000, Mattia Rossi mro...@swin.edu.au wrote: I'm using the patches from your website on my 8.2 box, which is the IPv6 gateway and runs rtadvd. The problem with the resolv.conf is happening on my client though, which is a box running HEAD, so I'll try to follow Doug's advice, thanks. Yes, you'll need the openresolv config in this case. Keep in mind that the resolver only queries at most MAXNS nameservers where MAXNS is usually 3. Using the openresolv name_servers_append, you need to make sure that your static servers are listed within the first MAXNS entries. If you have more than MAXNS dynamic servers, your statically configured ones will be ignored. I would just point out though that, in general, you shouldn't need static nameservers just because you have a manual IPv4 configuration. Nameservers will return both IPv4 and IPv6 addresses regardless of whether they were queried over 4 or 6. Of course, if you have an internal nameserver that has private info not available from the dynamically learned nameservers, then you will need a static config. Is there any chance that you could create a patch for 8.2 based on the commits in HEAD? That would be great! Better would be to ask hrs@ to MFC his commits to 8-stable. -jr signature.asc Description: PGP signature
Re: resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
On 05/08/2011 20:30, J.R. Oldroyd wrote: On Thu, 04 Aug 2011 23:52:54 -0700, Doug Bartondo...@freebsd.org wrote: On 08/04/2011 22:59, Mattia Rossi wrote: I've finally patched my 8.2 IPv6 gateway with the RDNSS/DNSSL patches The script anyhow overwrites my previous manual entries in /etc/resolv.conf which I need for my manual IPv4 setup... Check 'man resolvconf.conf' for information on name_servers_append. It would probably be nice if there was a _prepend equivalent. Mattia, when you say you have the patches, which ones? To be clear, the RDNSS/DNSSL support that was committed to head was very heavily modified from that which I proposed and which is on my web site. In particular, the resolvconf(8) tool that I offered was not used at all; the version in head is the openresolv tool by Roy Marples. Doug's response is in regard to the resolvconf version in head. I'm using the patches from your website on my 8.2 box, which is the IPv6 gateway and runs rtadvd. The problem with the resolv.conf is happening on my client though, which is a box running HEAD, so I'll try to follow Doug's advice, thanks. FWIW, the resolvconf version from my site will use the most recent nameservers received by from either dhclient-script or rtadvd but you can also add static entries using standard resolv.conf syntax in the /var/db/resolv.db file; see the man page with that version. I'll remember to read the manpages more thoroughly :-) I will update my RDNSS/DNSSL web page now to add a warning that my patches have been superseded and that folk should use the committed versions where possible. Is there any chance that you could create a patch for 8.2 based on the commits in HEAD? That would be great! Thanks, Mat ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
Hi all, I've finally patched my 8.2 IPv6 gateway with the RDNSS/DNSSL patches and I'm distributing DNS servers that way now. Works fine, my box running CURRENT picks up the DNS servers and search domains and writes them into /etc/resolv.conf using the resolvconf script. The script anyhow overwrites my previous manual entries in /etc/resolv.conf which I need for my manual IPv4 setup... I think it's an easily fixable bug - haven't looked into it that close atm., but given that the resolvconf script is going to be rewritten/enhanced anyways, that's something to keep in mind. I think that manual entries should always be preferred. Mat ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
On 08/04/2011 22:59, Mattia Rossi wrote: Hi all, I've finally patched my 8.2 IPv6 gateway with the RDNSS/DNSSL patches and I'm distributing DNS servers that way now. Works fine, my box running CURRENT picks up the DNS servers and search domains and writes them into /etc/resolv.conf using the resolvconf script. The script anyhow overwrites my previous manual entries in /etc/resolv.conf which I need for my manual IPv4 setup... I think it's an easily fixable bug - haven't looked into it that close atm., but given that the resolvconf script is going to be rewritten/enhanced anyways, that's something to keep in mind. I think that manual entries should always be preferred. Check 'man resolvconf.conf' for information on name_servers_append. It would probably be nice if there was a _prepend equivalent. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: resolvconf script overwrites entries in resolv.conf - RDNSS/DNSSL related
On Thu, 04 Aug 2011 23:52:54 -0700, Doug Barton do...@freebsd.org wrote: On 08/04/2011 22:59, Mattia Rossi wrote: I've finally patched my 8.2 IPv6 gateway with the RDNSS/DNSSL patches The script anyhow overwrites my previous manual entries in /etc/resolv.conf which I need for my manual IPv4 setup... Check 'man resolvconf.conf' for information on name_servers_append. It would probably be nice if there was a _prepend equivalent. Mattia, when you say you have the patches, which ones? To be clear, the RDNSS/DNSSL support that was committed to head was very heavily modified from that which I proposed and which is on my web site. In particular, the resolvconf(8) tool that I offered was not used at all; the version in head is the openresolv tool by Roy Marples. Doug's response is in regard to the resolvconf version in head. FWIW, the resolvconf version from my site will use the most recent nameservers received by from either dhclient-script or rtadvd but you can also add static entries using standard resolv.conf syntax in the /var/db/resolv.db file; see the man page with that version. I will update my RDNSS/DNSSL web page now to add a warning that my patches have been superseded and that folk should use the committed versions where possible. -jr signature.asc Description: PGP signature
