Invalid multi values domain string generated by network manager

[João Pinto]

I am getting the following error using nslookup:
nslookup: parse of /etc/resolv.conf failed
The file was not edited manually, it was generated by NM and the AT&T VPN Client.
I have changed the IPs/Domains for privacy reasons, /etc/resolv.conf:
#@NETVPN_GENERATED@ -- this file is generated by NetVPN
# and will be overwritten by NetVPN
# as long as the above mark is intact
nameserver 127.0.0.1
nameserver 127.0.0.1
# Generated by NetworkManager
domain local.domain.com br.somewhere.com somewhere.com
search local.domain.com
nameserver 127.0.0.1
nameserver 127.0.0.1
nameserver 127.0.0.1

[João Pinto (joaopinto)]

dnsutils:
  Installed: 1:9.5.0.dfsg.P2-1ubuntu2

[João Pinto (joaopinto)]

nslookup error message is related to the "domain local.domain.com br.somewhere.com somewhere.com", which is invalid.
The bug us with NetworkManager which is building an invalid multiple domain script.

[João Pinto (joaopinto)]

This turned to be an AT&T VPN client problem.
Setting NETVPN_DEF_DOMAIN to "" on /etc/agnclient/agnclient.conf fixed it.

[gwendo (mikael-lonneberg)]

This is actually not an issue with the Agnclient, it is the Comment line # Generated by NetworkManager in the middle of the file that is the problem. Remove that and it works like a charm.

[Alexander Sack (asac)]

João Pinto wrote:
> nslookup error message is related to the "domain local.domain.com br.somewhere.com somewhere.com", which is invalid.
> The bug us with NetworkManager which is building an invalid multiple domain script.
>
> ** Also affects: network-manager-applet (Ubuntu)
> Importance: Undecided
> Status: New
>
>
 affects ubuntu/network-manager-applet
 status invalid

this is a bug in NM

 affects ubuntu/network-manager
 status triaged

Can you please open a bug in bugzilla.gnome.org for that?

 affects network-manager
 status incomplete

thanks!

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Forwarded upstream

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Upstream considers this not being a bug in network-manager, but in the AT&T VPN Client. Don't know which package is the right one for that.

[Matt Keys (mk6032)]

I ran into this error on a different (CentOS 6 x86_64) system. Simply executing "nslookup" would return the error "nslookup: parse of /etc/resolv.conf failed". Upon close inspection of the contents nothing was out of order. Permissions and ownership also looked good and I was executing nslookup as root. It was then I noticed lsattr /etc/resolv.conf was showing the "e" flag set.

The customer had copied resolv.conf over from a different server (also ext4 formatted). I believe it may be that this attribute was set on the previous filesystem, and when moved to the new ext4 file system the extent mappings were incorrect, which caused the read/parse problem. Since you can't remove the attribute with chattr I was able to resolve the issue by simply copying the contents, deleting the old /etc/resolv.conf, creating a new /etc/resolv.conf, then pasting in the contents from clipboard and saving.