utilize
asked on
DNS Server Interface resets listening addresses
Hello,
We are experiencing a situation with a client whereby a DNS Servers list of Interfaces keeps resetting to listen on all IP addresses.
There are two DNS servers in the domain, both of which are domain controllers. Both servers have two network cards with different IP address ranges on each. The purpose of this is one for production and one for DR,
To prevent DNS issues on the network, the DNS servers are set to only listen for DNS requests on the IPv4 address of the production network. However, every now and then (usually following a reboot or DNS service restart) a 410 DNS event is logged and the DNS configuration changes to listen to requests on all interfaces. This results in clients trying to resolve IP addresses on the DR network.
The box to register this adapter in DNS has been un checked on both NICs.
Any guidance greatly received.
We are experiencing a situation with a client whereby a DNS Servers list of Interfaces keeps resetting to listen on all IP addresses.
There are two DNS servers in the domain, both of which are domain controllers. Both servers have two network cards with different IP address ranges on each. The purpose of this is one for production and one for DR,
To prevent DNS issues on the network, the DNS servers are set to only listen for DNS requests on the IPv4 address of the production network. However, every now and then (usually following a reboot or DNS service restart) a 410 DNS event is logged and the DNS configuration changes to listen to requests on all interfaces. This results in clients trying to resolve IP addresses on the DR network.
The box to register this adapter in DNS has been un checked on both NICs.
Any guidance greatly received.
Raj-GT
Even if you uncheck the register adapters options, the Netlogon service will still register itself in DNS every time you reboot. I don't think multihoming an AD+DNS server is supported. There is no easy way to fix this I'm afraid.
We have the same setup and this have never happen to us. The only thing I can think of is maybe there is something wrong with the actual DNS role on the server or possible getting the latest windows patches as this is not normal behavior.
Does this happen on both DNS servers? Few thing I would do below...
• install latest windows patches
• check the NIC binding order in advance options, make sure DR Nic is lowest priority
• Update the NIC drivers for the DR NIC
Thanks
Will.
Does this happen on both DNS servers? Few thing I would do below...
• install latest windows patches
• check the NIC binding order in advance options, make sure DR Nic is lowest priority
• Update the NIC drivers for the DR NIC
Thanks
Will.
ASKER
Hello,
Thank you for your comments. I can confirm that I have followed the procedures mentioned above prior to posting here.
To confirm:
All MS updates are installed with latest NIC drivers.
The binding order specifies the production LAN first
I have selected to only listen on the a specific address, as per the technet article.
Thank you,
Thank you for your comments. I can confirm that I have followed the procedures mentioned above prior to posting here.
To confirm:
All MS updates are installed with latest NIC drivers.
The binding order specifies the production LAN first
I have selected to only listen on the a specific address, as per the technet article.
Thank you,
reinstall DNS Role
ASKER
hello
have finally got around to reinstalling the DNS role on both DCs but still the problem happens.
I did this:
uninstalled DNS role
reboot
confirmed role uninstalled
reinstalled role
reboot
IP interfaces shows all IP addresses again.
Any further ideas please?
have finally got around to reinstalling the DNS role on both DCs but still the problem happens.
I did this:
uninstalled DNS role
reboot
confirmed role uninstalled
reinstalled role
reboot
IP interfaces shows all IP addresses again.
Any further ideas please?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Setting the DNS Server Service fixed the issue. Resolved with Microsoft Tech Support.