Comment 19 for bug 998712

Reggie: First of all, thanks for providing information about the malfunction on your system. We will get to the bottom of this!

To get very clear on what's happening I will summarize. Let me know if any of the following is wrong.

With the following resolv.conf (omitting comments)

    nameserver 127.0.0.1
    search home.lan

libc resolution of "lenin" repeatedly fails but "lenin.home.lan" repeatedly succeeds, whereas with

    nameserver 127.0.0.1
    nameserver 192.168.99.2
    search home.lan

both of them repeatedly succeed.

Dnsmasq listens at 127.0.0.1, configured with the following.

server=192.168.99.2
server=24.177.176.38
server=97.81.22.195

Only 192.168.99.2 can resolve the name "lenin.home.lan"; the others cannot.

Now, what's going on here?

First I'd like to rule out the possibility of side-effects of #1003842. Please eliminate the lines

server=24.177.176.38
server=97.81.22.195

from /run/nm-dns-dnsmasq.conf and run all your tests again. That is, repeatedly (at least twice) try "ping lenin" and "ping lenin.home.lan" both with only nameserver 127.0.0.1 listed in /etc/resolv.conf, and with nameserver 127.0.0.1 and nameserver 192.168.99.2 listed in /etc/resolv.conf. Report the results back here.

In the case where you add "nameserver 192.168.99.2" to /etc/resolv.conf and name resolution subsequently succeeds, is there a noticeable delay?

After you have edited /etc/resolv.conf, is /etc/resolv.conf still a symbolic link to /run/resolvconf/resolv.conf? That is, did you in fact edit /run/resolvconf/resolv.conf as I am assuming you did?

According to resolv.conf(5) the following environment variables can affect the behavior of the resolver: LOCALDOMAIN, RES_OPTIONS. Is either of these set in your environment? (Run, e.g., the

    env |grep '\(DOMAIN\|RES\)'

command to check this.)