after upgrading to network-manager to 0.7.0~svn4191-1 from 0.6.6-2, the search options in my resolv.conf are created incorrectly.

one issue is that the domains in the search path are separated by a "\032" instead of a space (this is also reported in Ubuntu Bug #275288).

the other issue is that resolvconf (apparently used in 0.6.6) was intelligent about merging domain and search lines.  this seems to have been lost now that network-manager has taken over the resolvconf functionality.

pre-upgrade (0.6.6-2) resolv.conf:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 207.241.238.254
nameserver 207.241.239.104
search sheridan.archive.org diatribes.org. us.archive.org. archive.org. .

post-upgrade (0.7.0~svn4191) resolv.conf:
# Generated by NetworkManager
domain sheridan.archive.org
search diatribes.org.\032us.archive.org.\032archive.org.\032.
nameserver 207.241.238.254
nameserver 207.241.239.104

andy bezella wrote:

Hi Andy,

could you please check, if you have configured domain-list correctly [1]
in dhclient.conf, i.e. lines end with a semicolon and
entries are enclosed in double quotes and separated by commas.



Thanks,
Michael


[1] https://bugzilla.redhat.com/show_bug.cgi?id=450042#c36

hi michael -

yep, that was my problem with the "/032" character.  the dhcp-options
man page in debian contradicts the snippet in the redhat link you sent:
  The domain-list data type specifies a list of domain names, a space
  between each name and the entire string enclosed in double quotes.
  These types of data are used for the domain-search option for example,
  and encodes an RFC1035 compressed DNS label list on the wire.

no mention of commas and it states that the _entire_ string should be
quoted.  once i added the commas and changed the quoting, network
manager created the resolv.conf search line without the "/032".

i'm unsure if i should file a bug against dhcp3-client re: the
documentation, as the format described in the man page seems to work
outside of network-manager.  do you have a suggestion?

thanks for your time.  let me know if you need me to supply any
additional information or try anything regarding the second part of this
bug (network manager's handling of the "domain" and "search" lines).

	andy
-- 
andrew bezella <abezella@archive.org>
Internet Archive

andrew bezella wrote:

I think the dhcp-options man page is outdated. See also [1].
I CCed Andrew, just to be sure.

Nonetheless, even if this is a misconfiguration, I talked to NM
upstream, and we discussed if NM could be a bit smarter and strip off
"/032". After all, it's not a valid domain name component.
Upstream does not seem to be aversed to this idea.

Andrew, what would be your recommendation?

Cheers,
Michael


[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492500#10

per the resolv.conf manpage, "The domain and search keywords are
mutually exclusive."  earlier versions of network-manager (using
resolvconf) respected this and merged domain and
search lines.  currently network-manager is creating both "search" and
"domain" keywords.  could / should this be changed?

thank you.

	andy

per the resolv.conf manpage, "The domain and search keywords are
mutually exclusive."  earlier versions of network-manager (using
resolvconf) respected this and merged domain and
search lines.  currently network-manager is creating both "search" and
"domain" keywords.  could / should this be changed?

thank you.

	andy