Dns сервер код ошибки 408

dears,

kindly note the below.

i had 2 2012r2 dcs and upgraded them to 2019.

2019 dcs took the ips of 2012r2 and the 2012r2 dcs are demoted.

ipconfig /registerdns was used on the new servers.

DNS a record is showing that the new servers has the old ips which is true.

deleted all records pointing to old dcs from my dns.

the issue is the following: i;m receiving errors on my new dcs: 

event 407:The DNS server could not bind a User Datagram Protocol (UDP) socket to (its own ip). The event data is the error code. Restart the DNS server or reboot your computer.

event 408: he DNS server could not open socket for address ( its own ip).
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.

i searched for some troubleshooting tips:

and i checked i only have on interface in each dc.

NS Manager -> Expand Forward Lookup Zones->right click _msdcs.domain.foo-> properties-> Name Servers-> point to itself.

the above was verified: on each dc the name server point to its ip address.

what could it be dears>

any idea

best regards,

Could you provide a screenshot of the issue or maybe explain it a little more? Just posting the technet article doesn’t really explain your precise issue, and may not even be the root cause. The more info you provide, the more help you can get.

nathan7757 wrote:

Basically can’t connect to internet via server. 
I’ve done tracert on both server and pc to which both completed and are identical just when loading a browser it won’t load anything.  

What is the IP config of the server? Have you checked your DNS forwarders?

I see a problem already. Look at your DNS config. It’s wrong.

How many DNS servers do you have? one, two, or more?

nathan7757 wrote:

Only one DNS server

The config is still wrong. The DNS is pointing to itself, and this is expected. However, if your forwarders are not set up correctly in DNS, then your server is not going to know who www.google.com Opens a new window is because it has no record locally when doing the lookup and no server to send the request on to.

Read this:

http://technet.microsoft.com/en-us/library/cc754941.aspx Opens a new window

I’m trying to setup AD/DNS on my new server running Windows 2012 R2. I’ve installed the roles, configured a static ip, made forward and reverse zones, etc. In the events list I see 408, 407, and 404 errors. When running dcdiag it fails on the connectivity test:

Testing server: Default-First-Site-NameDCName
   Starting test: Connectivity
      The host <numbers>._msdcs.domain.foo could not be resolved to an IP address. Check
      the DNS server, DHCP, server name, etc.
      Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
      ......................... DCName failed test Connectivity

I’m concerned that perhaps the ip address is not configured correctly should the static ip and «DNS server» be the same?

Could it perhaps have something to do with the fact this is running as a virtual machine isolated from the internet?

EDIT

Event Text:
407 The DNS server could not bind a User Datagram Protocol (UDP) socket to <server ip>. The event data is the error code. Restart the DNS server or reboot your computer.

408

The DNS server could not open socket for address <server ip>. 
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.

404

The DNS server could not bind a Transmission Control Protocol (TCP) socket to address <server ip>.  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.