Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #197595 > unrolled thread

Sid still getting retired DNS entry

Started byKent West <westk@acu.edu>
First post2018-07-13 18:40 +0200
Last post2018-07-13 21:10 +0200
Articles 11 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  Sid still getting retired DNS entry Kent West <westk@acu.edu> - 2018-07-13 18:40 +0200
    Re: Sid still getting retired DNS entry Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-13 18:40 +0200
      Re: Sid still getting retired DNS entry Curt <curty@free.fr> - 2018-07-13 19:00 +0200
      Re: Sid still getting retired DNS entry Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-13 19:00 +0200
      Re: Sid still getting retired DNS entry Kent West <westk@acu.edu> - 2018-07-13 19:00 +0200
        Re: Sid still getting retired DNS entry john doe <johndoe65534@mail.com> - 2018-07-13 19:10 +0200
          Re: Sid still getting retired DNS entry Kent West <westk@acu.edu> - 2018-07-13 19:10 +0200
            Re: Sid still getting retired DNS entry john doe <johndoe65534@mail.com> - 2018-07-13 19:40 +0200
              Re: Sid still getting retired DNS entry Kent West <westk@acu.edu> - 2018-07-13 20:40 +0200
                Re: Sid still getting retired DNS entry Greg Wooledge <wooledg@eeg.ccf.org> - 2018-07-13 20:50 +0200
                  Re: Sid still getting retired DNS entry Kent West <westk@acu.edu> - 2018-07-13 21:10 +0200

#197595 — Sid still getting retired DNS entry

FromKent West <westk@acu.edu>
Date2018-07-13 18:40 +0200
SubjectSid still getting retired DNS entry
Message-ID<wb9gR-6Js-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

In my org, a DNS server was recently retired, but my /etc/resolv.conf is
still being populated with the old DNS entry (which slows my networking
considerably; I can delete that line manually, but that's just a temporary
fix).

My network admin tells me that I have a "dhcp-static" address, and "it
shows to have the correct dns info at the server. If you are getting
network settings from DHCP and they aren't manually configured, you should
have the correct settings from what I am seeing."

My /etc/network/interfaces:

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



and

westk@westkent:~$ ls -lah /etc/network/interfaces.d/
> total 8.0K
> drwxr-xr-x 2 root root 4.0K Mar 13  2015 .
> drwxr-xr-x 7 root root 4.0K Jul 13 07:39 ..



Any suggestions as to what's going on? Thanks!


-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [next] | [standalone]

#197596

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2018-07-13 18:40 +0200
Message-ID<wb9gS-6Js-11@gated-at.bofh.it>
In reply to#197595
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.

[toc] | [prev] | [next] | [standalone]

#197597

FromCurt <curty@free.fr>
Date2018-07-13 19:00 +0200
Message-ID<wb9Ad-6QO-1@gated-at.bofh.it>
In reply to#197596
On 2018-07-13, Greg Wooledge <wooledg@eeg.ccf.org> 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.
>
>

NetworkManager informs me here that it has taken control of
/etc/resolv.conf:

curty@einstein:~$ cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 192.168.0.254

So I guess the OP would know if it's nm or not.

[toc] | [prev] | [next] | [standalone]

#197598

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2018-07-13 19:00 +0200
Message-ID<wb9Ad-6QO-5@gated-at.bofh.it>
In reply to#197596
On Fri, Jul 13, 2018 at 11:50:22AM -0500, Kent West wrote:
> 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
> 
> So I would agree with you. But where do I look to find the problem?

Find whoever set up this system and get them to tell you how they did it.

Failing that, you could TRY setting up the interface in /e/n/i and see
if that undoes whatever the other thing is.  If there even is an other
thing.  Maybe there really isn't anything managing the interface AT ALL
and it's only running because the previous admin brought it up by hand
with raw "ip" commands and the system hasn't been rebooted since then.

Who the hell knows.

[toc] | [prev] | [next] | [standalone]

#197599

FromKent West <westk@acu.edu>
Date2018-07-13 19:00 +0200
Message-ID<wb9Ad-6QO-7@gated-at.bofh.it>
In reply to#197596

[Multipart message — attachments visible in raw view] — view raw

On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge <wooledg@eeg.ccf.org> 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

So I would agree with you. But where do I look to find the problem?

Thanks!


-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [next] | [standalone]

#197601

Fromjohn doe <johndoe65534@mail.com>
Date2018-07-13 19:10 +0200
Message-ID<wb9JU-79U-3@gated-at.bofh.it>
In reply to#197599
On 7/13/2018 6:50 PM, Kent West wrote:
> On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge <wooledg@eeg.ccf.org> 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)?

What is the output of:

$ cat /etc/resolv.conf

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#197602

FromKent West <westk@acu.edu>
Date2018-07-13 19:10 +0200
Message-ID<wb9JU-79U-5@gated-at.bofh.it>
In reply to#197601

[Multipart message — attachments visible in raw view] — view raw

On Fri, Jul 13, 2018 at 12:00 PM, john doe <johndoe65534@mail.com> wrote:

> On 7/13/2018 6:50 PM, Kent West wrote:
>
>> On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge <wooledg@eeg.ccf.org>
>> 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?




-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [next] | [standalone]

#197603

Fromjohn doe <johndoe65534@mail.com>
Date2018-07-13 19:40 +0200
Message-ID<wbacV-7ke-7@gated-at.bofh.it>
In reply to#197602
On 7/13/2018 7:04 PM, Kent West wrote:
> On Fri, Jul 13, 2018 at 12:00 PM, john doe <johndoe65534@mail.com> wrote:
> 
>> On 7/13/2018 6:50 PM, Kent West wrote:
>>
>>> On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge <wooledg@eeg.ccf.org>
>>> 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)
2)  Remove any configuration relative to DNS (/etc/network/interfaces ...)
3)  Restart NM
4)  The file /etc/resolv.conf should be populated with the DNS given by 
your dhcp server

You might have some luck looking in the directory:

/var/lib/dhcp

-- 
John Doe

[toc] | [prev] | [next] | [standalone]

#197604

FromKent West <westk@acu.edu>
Date2018-07-13 20:40 +0200
Message-ID<wbb90-7UN-3@gated-at.bofh.it>
In reply to#197603

[Multipart message — attachments visible in raw view] — view raw

On Fri, Jul 13, 2018 at 12:31 PM, john doe <johndoe65534@mail.com> wrote:

> On 7/13/2018 7:04 PM, Kent West wrote:
>
>> On Fri, Jul 13, 2018 at 12:00 PM, john doe <johndoe65534@mail.com> wrote:
>>
>> On 7/13/2018 6:50 PM, Kent West wrote:
>>>
>>> On Fri, Jul 13, 2018 at 11:36 AM, Greg Wooledge <wooledg@eeg.ccf.org>
>>>> 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

[toc] | [prev] | [next] | [standalone]

#197605

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2018-07-13 20:50 +0200
Message-ID<wbbiF-7YA-1@gated-at.bofh.it>
In reply to#197604
On Fri, Jul 13, 2018 at 01:33:41PM -0500, Kent West wrote:
> I renamed /etc/network/interfaces.

Put it back!!

It contains the configuration for loopback (lo) which is really important.

Your interface was NOT listed in /e/n/i so Network Manager grabbed it and
took over.

You can see this by the way /etc/resolv.conf had been turned into a symlink
with "Network Manager" in the name, and by the way the contents of that
symlink said "Network Manager was here".

[toc] | [prev] | [next] | [standalone]

#197606

FromKent West <westk@acu.edu>
Date2018-07-13 21:10 +0200
Message-ID<wbbC2-8kQ-13@gated-at.bofh.it>
In reply to#197605

[Multipart message — attachments visible in raw view] — view raw

On Fri, Jul 13, 2018 at 1:46 PM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Fri, Jul 13, 2018 at 01:33:41PM -0500, Kent West wrote:
> > I renamed /etc/network/interfaces.
>
> Put it back!!
>
> It contains the configuration for loopback (lo) which is really important.
>
> Your interface was NOT listed in /e/n/i so Network Manager grabbed it and
> took over.
>
> You can see this by the way /etc/resolv.conf had been turned into a symlink
> with "Network Manager" in the name, and by the way the contents of that
> symlink said "Network Manager was here".
>
>
Already put back to the way it's supposed to be.

Welp, this has been educational, although I didn't get all the answers I
wanted. But we can stop now, because ... DUH! ... why don't I try a
different computer on this same wire?

And behold! It gets the bad DNS entry also.

I'll go back to my network admin now, and pester him.

Thanks anyway, all!


-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web