Symptoms
-
IP address was changed more than 48 hours ago, however, the domain still points to the old IP while in Domains > example.com > DNS Settings all records point to a new IP address.
-
The following records are shown in the Event Viewer:
The DNS server could not open socket for address 203.0.113.2.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNSParameters ListenAddress value in the services section of the registry and restart.)
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.
For more information, see "DNS server log reference" in the online Help.
The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 203.0.113.2. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.
The DNS server could not bind a User Datagram Protocol (UDP) socket to 203.0.113.2. The event data is the error code. Restart the DNS server or reboot your computer.
Cause
Records in the server's DNS Manager show the old IP address and were not updated by changes in the Plesk > Domains > example.com > DNS Settings.
Resolution
- Connect to the server via RDP.
- Go to Server manager > Tools > DNS server > Select DNS server > right-click and Properties > Interfaces tab.
- Check the IP addresses and unselect not used one.
- Log in to Plesk.
- Restart DNS server at Tools & Settings > Service management.
with