On Fri, Jul 13, 2018 at 12:31 PM, john doe <[email protected]> wrote:
> On 7/13/2018 7:04 PM, Kent West wrote: > >> On Fri, Jul 13, 2018 at 12:00 PM, john doe <[email protected]> wrote: >> >> On 7/13/2018 6:50 PM, Kent West wrote: >>> >>> On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge <[email protected]> >>>> wrote: >>>> >>>> On Fri, Jul 13, 2018 at 11:29:42AM -0500, Kent West wrote: >>>> >>>>> >>>>> westk@westkent:~$ cat /etc/network/interfaces >>>>>> >>>>>> # This file describes the network interfaces available on your system >>>>>>> # and how to activate them. For more information, see interfaces(5). >>>>>>> source /etc/network/interfaces.d/* >>>>>>> # The loopback network interface >>>>>>> auto lo >>>>>>> iface lo inet loopback >>>>>>> >>>>>>> >>>>>> Well, if the interface isn't being configured in /e/n/i then either >>>>> it's >>>>> using NetworkManager or it's using systemd-networkd. Or something that >>>>> you set up by hand. >>>>> >>>>> >>>>> westk@westkent:~$ ps as | grep NetworkManager >>>>> >>>> 1000 11085 0000000000000000 0000000000000000 0000000000000000 >>>> 0000000180000000 S+ pts/0 0:00 grep NetworkManager >>>> westk@westkent:~$ ps as | grep systemd-networkd >>>> 1000 11088 0000000000000000 0000000000000000 0000000000000000 >>>> 0000000180000000 S+ pts/0 0:00 grep systemd-networkd >>>> >>>> >>>> 'systemd-resolved' will handle your DNS. >>> >>> Is /etc/resolv.conf a symlink (if yes, to where)? >>> >>> >> westk@westkent:~$ ls -lah /etc/resolv.conf >> lrwxrwxrwx 1 root root 31 Jul 13 11:22 /etc/resolv.conf -> >> /run/NetworkManager/resolv.conf >> >> >> >> What is the output of: >>> >>> $ cat /etc/resolv.conf >>> >>> >>> westk@westkent:~$ cat /etc/resolv.conf >> # Generated by NetworkManager >> search acu.local >> nameserver 150.252.131.127 >> nameserver 150.252.134.8 >> nameserver 150.252.134.159 >> >> (this is after I manually removed the bad entry and replaced it with the >> good) >> >> >> Is there a way to test, from my client, what my ord's DHPC server is >> giving >> me for DNS entries, to double-check my network admin's findings? >> >> > Possibly, but I don't know how NM works. > > Some hints: > > The best way is to be sure of what the dhcp server is dishing out assuming > you can access it. > > If you are ready to get dirty and break your "system": > > 1) Empty /etc/resolv.conf (clear the content of the file, that way, you > don't remove the symlink) > I made a backup of the file, and then emptied /etc/resolv.conf, saving it back as an empty file. > 2) Remove any configuration relative to DNS (/etc/network/interfaces ...) > I renamed /etc/network/interfaces. > 3) Restart NM > I ran /etc/init.d/network-manager stop followed by /etc/init.d/network-manager start > 4) The file /etc/resolv.conf should be populated with the DNS given by > your dhcp server > The /etc/resolv.conf is back to where it started, with the bad entry. So, either my network admin is wrong about what his configuration is feeding to my box, or there's something between his server and my NetworkManager that is misconfigured. > > You might have some luck looking in the directory: > > /var/lib/dhcp > > The only thing here is an empty dhclient.leases file. > -- > John Doe > > -- Kent West <")))>< Westing Peacefully - http://kentwest.blogspot.com
