Comment 21 for bug 1169437

Revision history for this message
Thomas Hood (jdthood) wrote : Re: network-manager dnsmasq openvpn DNS issue

Clemens wrote in comment #13:

> My NetworkManager OpenVPN configuration had a domain listed under "Additional search domains".
> With dns=dnsmasq this resulted in the domains pushed from openvpn via 'push
> "dhcp-option DOMAIN mydomain"to be ignored.

I have just tried to reproduce this and cannot.

I have "dns=dnsmasq" and am initially not connect to a VPN. My resolv.conf looks like the following.

    # 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 127.0.1.1
    search myhomelandomain

I connect to my work VPN.

    # 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 127.0.1.1
    search mycorp.com myhomelandomain

I disconnect from the VPN. In the connection editor I add an "Additional search domain" and connect to the VPN.

    # 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 127.0.1.1
    search mycorp.com foobarbaz myhomelandomain

This is what I would expect. It seems that this bug is fixed too. Or there is a bug but it only manifests itself under certain circumstances. Clemens, if you still encounter this problem then please open a new bug report against network-manager-openvpn including details about the circumstances under which adding an "Additional search domain" causes the OpenVPN server supplied search domains to be omitted from the domain search list.