Other than "Resolver Configuration", where is WHM storing nameservers?

[zefie]

I once had IPv6 support on my cPanel/WHM VM. I migrated the VM to another server (and kept the same IPv4 addresses (same host same datacenter)), but chose to not give the VM IPv6 this time (as I have no local support for it with my ISP and am still unfamiliar with proper IPv6 security).

As such, the old configuration had a IPv4 and IPv6 nameserver in resolv.conf. Once in a while I get an email about DNS lookups failing using the IPv6 address (naturally since the VM does not have IPv6 now).

I go to "Resolver Configuration" and remove the IPv6 entry, and this stops the emails for a few days, until WHM randomly restores that IPv6 resolver entry again, and the emails start again.

So I am wondering how to actually remove a nameserver, since the "Resolver Configuration" seems to only be temporary.

This server does not have DHCP.

 

[cPanelMichael]

Hello,

The resolvers are configured in the /etc/resolv.conf file and that's where WHM detects them from. Are the new resolvers appearing after a reboot?

Thank you.

 

[zefie]

Hello,

The resolvers are configured in the /etc/resolv.conf file and that's where WHM detects them from. Are the new resolvers appearing after a reboot?

Thank you.

I figured it was standard, but yes, somehow its reappearing after security reboots. There are no IPv6 addresses defined (I removed it from the pool in WHM). Yet for some reason every time I replace the IPv6 address in the resolver configuration page, and reboot, it comes back.

 

[cPanelMichael]

Hello,

The following third-party URL should point you in the right direction:

CentOS 6 - nameserver entry in resolve.conf resetting after restarting network services?

Let us know if this helps.

Thank you.

 

[zefie]

Thank you for the response. I found some remains of the IPv6 config in the ifcfg and believe that may have been the cause. I removed it, as well as manually removed the nameserver (again) from resolv.conf. This likely will solve the issue although I won't know until the next security update reboot.

Thank you for pointing me in the right direction, and apologies, since I should have checked this.