DNS client entry keeps updating on each startup up on activation from saved state

Submitted by laurencefass on Fri, 02/06/2015 - 04:32

Hi.

This problem is related to the path:

Webmin=>Networking=>Network Configuration=>Hostname and DNS client=>DNS Servers.

I recently changed my DNS server to a remote machine (to run some tests).

I have completed tests so I am now including the IP address of my local machine so I can access Virtual Server domain names from the browswer.

(minor) problem: each time I power up or activate from saved state its resetting itself to the previous (unwanted) value. Virtualmin is clearly saving and retrieving state

Status: 
Active

Comments

Submitted by JamieCameron on Fri, 02/06/2015 - 16:17

Is your system setup to get its IP address from DHCP? If so, the DHCP server is probably specifying the IP address.

I'd recommend switching to a static IP configuration instead, especially for a system that is hosting websites.

Submitted by laurencefass on Mon, 02/09/2015 - 03:35

thanks for your assistance... its got a static IP address... The problem is not a change of the IP addresss - its a reset the list of the DNS server list on each wake or power up.

Submitted by JamieCameron on Mon, 02/09/2015 - 15:50

Once you configure your system to use a static IP, this will also prevent the DNS servers from being set by DHCP at startup (which I think is the cause of your problems).

Submitted by laurencefass on Tue, 02/10/2015 - 03:36

the problem was (long forgotten) manual entries in the etc/resolv.conf file overriding webmin settings. problem solved. thanks for your advice.

Submitted by laurencefass on Mon, 02/16/2015 - 07:18

opening again. it looks like there is a conflict between webmin and Linux Network Manager. The resolv.conf file is being updated by the NM automatically.

Submitted by andreychek on Mon, 02/16/2015 - 09:58

You're not seeing a conflict there -- Webmin/Virtualmin is just letting you know that it's a problem if your DNS servers are being overwritten.

There are some causes for that issue, along with solutions, mentioned in the documentation here in the section "Received Virtualmin error that 127.0.0.1 isn't listed in /etc/resolv.conf":

https://www.virtualmin.com/documentation/dns/faq

If you had any followup questions, since it looks like you're using Virtualmin GPL there, we'd suggest using the Forums to obtain support. We monitor the Forums, along with lots of wonderful folks in the community!

When opening a new Forum post regarding this issue, let us know what the contents of your /etc/network/interfaces file looks like, along with whether your server is a VPS or a dedicated server. If it's a VPS, what kind of VPS? Thanks!

Submitted by laurencefass on Mon, 02/23/2015 - 04:04

i am still having the problem... if possible i would like to resolve this here, else i will have to start again in the forum. i assure you all new posts will go to forum.

Im not using DHCP and I have assigned a static IP. ifconfig shows...

eth1 Link encap:Ethernet HWaddr 08:00:27:4e:22:2e
inet addr:192.168.200.100 Bcast:192.168.200.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe4e:222e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:217067 errors:0 dropped:0 overruns:0 frame:0 TX packets:73790 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:243539232 (232.2 MiB) TX bytes:24434452 (23.3 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1212028 errors:0 dropped:0 overruns:0 frame:0 TX packets:1212028 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0

each time i restore my VM (from power off or sleep), webmin loses my nameserver even though resolv.conf looks fine on startup/restore. my resolv.conf as follows...

groupspace4@host100:/home/gs4/sites/all/modules$ cat /etc/resolv.conf nameserver 192.168.200.100 nameserver 192.168.1.254 domain 192.168.200.100

Submitted by andreychek on Mon, 02/23/2015 - 10:39

Webmin and Virtualmin don't change the /etc/resolv.conf file, unless told to do so via the GUI.

The most common cause for what you're seeing is when an interface is configured to use DHCP, though it's possible another network-related service is causing the problem.

What is the output of this command:

cat /etc/network/interfaces

Submitted by laurencefass on Mon, 02/23/2015 - 10:51

thanks i appreciate your help.

$ 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).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 192.168.200.100
netmask 255.255.255.0
network 192.168.200.0
broadcast 192.168.200.255
gateway 192.168.200.1