severity normal
thanks
Hans-J. Ullrich wrote:
> Dear Maintainer,
I am not the maintainer. I am simply another long time user.
> either I misunderstood resolvconf or I resolvconf does not recognize dns
> entries.
> In /etc/network/intefaces I have
I believe you are misunderstanding how resolvconf is supposed to
work. That is why I have reduced the severity to normal. Because
what you describe is the way things are supposed to work. If after
the discussion you disagree feel free to change the severity again.
> dns-nameserver 208.67.222.222
> dns-nameserver 208.67.220.220
Okay.
> But /etc/resolv.conf is showing me this:
>
> ------snip -----
>
> # 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.0.1
>
>
> -------- snap --------
You don't say but the presence of 127.0.0.1 in that file leads me to
believe that you have a nameserver such as bind9 or other installed.
Because of that the startup for it is placing 127.0.0.1 in the
resolv.conf file. That is the normal and expected behavior.
If you stop the nameserver (in the case of bind9 anyway) then the
127.0.0.1 will be removed from that file. If you start the nameserver
again then 127.0.0.1 will be returned into the file.
If you want to see the IP addresses listed in the resolv.conf file
directly then stop or unistall whichever nameserver daemon (bind9?)
you have installed and running.
> IMO the entries for 208.67.222.222 and 208.67.220.220 should also
> appear in resolv.conf.
No. That is not desired. Things would not work very well that way.
The libc resolver library only consults the very first nameserver
entry in the resolv.conf file. If that entry returns a result then
lookup stops there. Only if the first entry times out does the libc
resolver proceed to a subsequent entry. Up to three may be listed but
in order to get to the third one it would have had two long timeouts
first.
When using a local nameserver such as you have on 127.0.0.1 you would
normally have only one entry. Since it is running locally it is
expected not to fail. It will return an answer to the query. I will
keep assuming bind9 for the discussion until I learn otherwise. And
of course other nameservers will have their own unique configuration.
The /usr/share/doc/resolvconf/README.gz lists this:
3.5 bind9
* To make bind9 supply its nameserver address 127.0.0.1 to resolvconf,
set RESOLVCONF=yes in /etc/default/bind9.
When running with a local caching nameserver more configuration is
needed. See the README file for all of the details.
> However, they appear in dhcp.conf.
Are you talking about the DHCP server?
> Is this a bug or is this correct this way?
It is not a bug. It is the correct way.
> And is it recommended to use resolvconf in changing environments or
> should resolvconf be uninstalled?
I recommend resolvconf. I use it on all of my desktops, laptops, and
servers.
Bob
