search options in resolv.conf are separated by \032 instead of a blank

[Philipp Ehses]

Binary package hint: network-manager

NetworkManager creates a faulty resolv.conf on my university computer. It worked before with hardy (and also with earlier versions of intrepid) so I don't think it's a problem with the dhcp server. The automatically created resolv.conf looks like this (i removed ips and changed domain names):

# Generated by NetworkManager
domain domain1.de
search domain1.de\032domain2.de\032domain3.de
nameserver x.x.x
nameserver x.x.x

As you can see, the search domains are separated by \032 instead of a simple blank. Therefore I have to add the domain name in order to reach a computer on my network (or change the faulty line in resolv.conf after each reboot...). A minor annoyance which I can live with or can fix by myself but I'm wondering if anybody else experiences a similar problem?

[Sheldon Hearn (sheldonh)]

Interesting. I just get the first search value from my DHCP prepend list, rather than all of them separated with the wrong character.

What do you have in your dhclient.conf? I have:

prepend domain-search "dom1.com", "dom2.com", "dom3.com", "dom4.com";
request subnet-mask, broadcast-address, time-offset, routers,
        domain-name, domain-name-servers, domain-search, host-name,
        netbios-name-servers, netbios-scope, interface-mtu;

Ubuntu 8.10 (i386)
===========
dhcp3-client 3.1.1-1ubuntu2
ifupdown 0.6.8ubuntu12
lsb-base 3.2-14ubuntu2
netbase 4.32ubuntu1
net-tools 1.60-19ubuntu3
network-manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1

Ciao,
Sheldon.

[Sheldon Hearn (sheldonh)]

Please disregard my findings above. Although that dhclient.conf syntax worked for me under Debian Sid, it's not the documented syntax for domain-list values as per dhcp-options(5) on Ubuntu.

With the following, I get the same behaviour as described by the original poster:

prepend domain-search "dom1.com dom2.com dom3.com dom4.com";

Ciao,
Sheldon.

[Igor (xrevolver)]

Confirm that same bug relevant for Ubuntu 9.04.

Fixed in debian and fix indeed working on 9.04:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461056