Hello,
We have four DNS-Only cpanel servers that are used for hosting the DNS of all our shared web servers.
ns1.ourdomain.com
ns2.ourdomain.com
ns3.ourdomain.com
ns4.ourdomain.com
The IP address for "ns2" has changed, but it doesn't seem to be reflected in any of the DNS Cluster configuration for the associated web servers. We're getting emails from all our associated web servers saying:
When I log into the WHM for one of our web servers and go to the "DNS Cluster", it lists the four DNS servers, but shows the old IP address in the IP Address column. When I choose "Actions->Edit" for the nameserver, I can see that it correctly has:
--------------
Remote cPanel & WHM DNS host: ns2.ourdomain.com
--------------
So it seems that the WHM DNS Cluster system is not properly getting the new IP address that is now set for ns2.ourdomain.com.
Is there something we need to do to fix that? Is it a bug, or by design?
Thanks!
We have four DNS-Only cpanel servers that are used for hosting the DNS of all our shared web servers.
ns1.ourdomain.com
ns2.ourdomain.com
ns3.ourdomain.com
ns4.ourdomain.com
The IP address for "ns2" has changed, but it doesn't seem to be reflected in any of the DNS Cluster configuration for the associated web servers. We're getting emails from all our associated web servers saying:
Does anyone know what is necessary to change the ns2 IP address? Here is what we have done:DNS cluster errors on web1.ourdomain.com
- Changed "A" record DNS for "ns2.ourdomain.com" so it uses the new IP address.
- Updated the nameserver registration with InterNIC so this private nameserver uses the new IP address.
When I log into the WHM for one of our web servers and go to the "DNS Cluster", it lists the four DNS servers, but shows the old IP address in the IP Address column. When I choose "Actions->Edit" for the nameserver, I can see that it correctly has:
--------------
Remote cPanel & WHM DNS host: ns2.ourdomain.com
--------------
So it seems that the WHM DNS Cluster system is not properly getting the new IP address that is now set for ns2.ourdomain.com.
Is there something we need to do to fix that? Is it a bug, or by design?
Thanks!