Re: peerdns reversed?

[Dan Williams <dcbw redhat com>]

On Sun, 2014-04-20 at 21:15 -0400, Sean Darcy wrote:
> on Fedora 20:
>
> cat /etc/sysconfig/network-scripts/ifcfg-external
> # Please read /usr/share/doc/initscripts-*/sysconfig.txt
> # for the documentation of these parameters.
> TYPE=Ethernet
> BOOTPROTO=dhcp
> DEVICE=external
> DEFROUTE=yes
> IPV4_FAILURE_FATAL=no
> IPV6INIT=no
> PEERDNS=no
> DNS1=127.0.0.1
> DNS2=8.8.8.8
> ## PEERROUTES=yes
> USERCTL=no
>
> cat /etc/resolv.conf
> # Generated by NetworkManager
> nameserver 127.0.0.1
> nameserver 8.8.8.8
>
> but if I set PEERDNS=yes:
>
> cat /etc/resolv.conf
> # Generated by NetworkManager
> nameserver 167.206.251.130
> nameserver 167.206.251.129
> nameserver 127.0.0.1
> # NOTE: the libc resolver may not support more than 3 nameservers.
> # The nameservers listed below may not be recognized.
> nameserver 8.8.8.8
>
> Isn't this the wrong way around?

Currently any additional static DHCP servers are appended to those
detected from DHCP.  So I think this is the intended functionality.  I'm
assuming you'd rather have them prepended instead?

But since you're using 127.0.0.1, it seems unlikely that you want any
nameservers at all, but you'll want to use a local caching nameserver?
NM has some built-in functionality for that already using dnsmasq, see
'man NetworkManager.conf' in the section about DNS.

Dan