Named not resolving on reboot after VM Migration

Issues related to configuring your network
Post Reply
imperimus
Posts: 2
Joined: 2020/09/06 09:34:51

Named not resolving on reboot after VM Migration

Post by imperimus » 2020/09/06 09:46:14

Hi All,

I have had a dig around so hopefully this is not a dupe!

I have just done a VMWare vm migration of my DNS and DHCP server. This process created a new network card called ens33 instead of the previous ens160. I have changed the network configuration and DHCP config so the new hardware and network config is being used. DHCP is now working fine as does the rest of the system.

However when the system reboots although Named seems to start without error it does not respond to queries. However without changing anything if i simply restart the named service (systemctl restart named) it instantly responds to queries.

I have changed the service config to wait for network.online but this has not made any difference.

I have added a cron job to restart this after startup to work around the issue but would like to fix it properly if any one can help.

Thanks in advance!

User avatar
TrevorH
Forum Moderator
Posts: 29493
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Named not resolving on reboot after VM Migration

Post by TrevorH » 2020/09/06 14:56:50

Try adding LINKDELAY=10 to the /etc/sysconfig/network-scripts/ifcfg-$interface file for your interface.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

imperimus
Posts: 2
Joined: 2020/09/06 09:34:51

Re: Named not resolving on reboot after VM Migration

Post by imperimus » 2020/09/06 15:21:55

TrevorH wrote:
2020/09/06 14:56:50
Try adding LINKDELAY=10 to the /etc/sysconfig/network-scripts/ifcfg-$interface file for your interface.
Seems to have resolved the issue, thank you.

User avatar
TrevorH
Forum Moderator
Posts: 29493
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Named not resolving on reboot after VM Migration

Post by TrevorH » 2020/09/06 15:41:51

It would probably recover on its own if you left it long enough. Bind wakes up every now and then and scans for available network interfaces that are not in use and adds them but it does so on a configurable interval.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

Post Reply

Return to “CentOS 7 - Networking Support”