DNS server errors 404, 407, 408 when windows server installed on SSD

Babak Ebrahimi 21

Hey Guys!

I have a weird problem, when i install a windows server 2016 or 2019 on an SSD drive and setup the DNS server service (no more, just DNS) with or without DNS configuration, after restart the windows, DNS server reports 8 errors of 3 types 404, 407 and 408

Here is the errors contents:

(Ignore the IP addresses difference between this screenshot and text below, this was from another test)

407: The DNS server could not bind a User Datagram Protocol (UDP) socket to 192.168.1.10. 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 192.168.1.10.
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 DNS\Parameters\ 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 192.168.1.10. 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.

When i do the same process on the HDD, there is no problem at all, also i tried this with an old Computer with a regular dual core CPU, there was no problem, but on 3 different PCs with 3 types of intel Core i5 CPUs (3rd, 4th and 8th generations) i have the same errors

I tried different local static IP addresses, DSL Modems, NICs, and every solution i found about these errors on the internet, nothing has changed.

Anybody has any idea about the cause of problem?

And one more thing, last time i did the same process on a PC with a Crucial "CT240BX500SSD1" SSD, but there was no problem at all, this time i tried 3 different SSD brands (Samsung, Lexar and WD) the result was the same

I attached an screenshot from the errors to this question, maybe it'll help.

7 answers

Babak Ebrahimi 21 Reputation points

2020-12-11T23:54:04.583+00:00

Guys, i tried an M2 PCI-Express SSD the result was the same, i installed the Linux ubuntu server there was no problem with DNS server, but on the windows...

looks like the windows DNS server has a problem with any type of SSD drive! at least on the normal computers (I didn't test on the intel Xeon Processors yet)
Please sign in to rate this answer.
Frank Walder 1 Reputation point

2022-01-22T04:22:46.793+00:00

I have been running Windows Server 2016 Standard on a HP DL380 Gen 9 since November 2019. My server runs 2 x Xeon E5-2667v3 CPUs with 256Gb of RAM.
DNS has never completely worked correctly, and I have many Error 404, 407, and 408 in my log files to remind me of the failing. I do not run AD on this server and do not run AD on my LAN. I do have Hosts files on the two Windows 10 Pro machines and the server, but not on the Macintosh. The Windows 10s have spinning rust (SATA HDD) to boot from, and work using NetBios over TCP/IP. The server boots from a Samsung 970 Pro NVMe on a PCIe card. Are you saying I have to go back to HDDs on my server to get my DNS working, or can I at least use 2.5" SSDs through my SAS controller?

Babak Ebrahimi 21 Reputation points

2022-01-22T04:39:17.207+00:00

In my experience DNS server didn't work on any type of SSD drive, i had to go back to HDD
I don't know maybe you could use virtualization or something to fix this problem on SSD drives but installing windows server Directly on SSD drive didn't work for me (the problem was DNS server of course, not just installing the OS)

Frank Walder 1 Reputation point

2022-01-23T10:14:43.423+00:00

Since my last comment regarding your DNS installs I tried setting up a Win Serv 16 w/DNS on a spare machine, with a 1Tb 3.5" SATA HDD. There were still many of the same problems as with the NVMe M.2 install, but I was able to get it working, being able to perform local quarries, recursive quarries and zone replication. A vender about 200km away offered to sell be ten refurbed 1Tb 10K SAS3 HDDs for about $80 USD this past Fall. Since my experiment supports your conclusion, I might see if that deal is still available. My regret is that 10K 'spinning rust' is a waste of SAS3 bandwidth.

Babak Ebrahimi 21 Reputation points

2022-01-23T12:01:40.293+00:00

I didn't test SAS my friend
I just tested the normal SATA HDD and that solved my problem, I don't know if SAS storages could cause the same problem as SSD or not

Frank Walder 1 Reputation point

2022-01-23T12:27:41.97+00:00

I assume our issue is with the storage medium, ergo Solid state NVMe or SSD versus HDD. The 'bus', ergo SATA or SAS should not be part of the problem. My DNS worked on HDD storage on a SATA bus, which replicated your results. It has not worked on an NVMe(chips) on a PCIe bus. I was not testing for the type of bus, only the type of storage. If we explore the bus architecture, then we may need to evaluate the drive controllers as well for compatibility. The question then becomes was your success due to using an HDD or due to you using a SATA bus?
Sign in to comment
henry chen 1 Reputation point

2021-04-21T10:14:43.907+00:00

i installed only dns server on a new installed windows server 2019,i also get the 404,407,408 error when the dns server used as a only root.hint server;but when i add a forwarder server 8.8.8.8 onto the dns server ,it can resolve the the address,i don't know why?
Please sign in to rate this answer.
Babak Ebrahimi 21 Reputation points

2022-01-22T04:44:17.847+00:00

That doesn't work for me, DNS server has issues on SSD drive when the windows server has installed directly on hardware, maybe Virtualization could get different results I don't know

Frank Walder 1 Reputation point

2022-01-22T06:03:01.633+00:00

I was able to get Internet resolution when I installed DNS forwarding onto the Zone server to 208.67.222.222 and 208.67.220.220. This the same machine I described above in my reply to BabakEbrahimi-3629. I still have no resolution of local address on my LAN.
Sign in to comment

Share via

DNS server errors 404, 407, 408 when windows server installed on SSD

7 answers