We have a small network, with a main server (hosting our own website and functioning as a name server) and some web hosting servers. Since yesterday we have an issue with a domain of a client of ours that we host on our network.
The webserver is set up correctly, the name server as well (and both work fine for other domains), but the domain is unreachable because the hostname lookup fails. Chrome says the hostname could not be resolved, some DNS check tools say that the domain could not be found or even simply just crash.
When I run the
dig directgeslaagd.com command, I get an authority section only, saying
com 600 IN SOA a.gtld-... which is for the TLD. When I run the
dig @ns1.webwhales.nl directgeslaagd.com command, I get the right results (
directgeslaagd.com. 86400 IN A 188.8.131.52). This happens from both inside and outside our server network. So, my conclusion is that my name server works correctly, right?
When I adjust the hosts file of my windows PC and load this domain from 184.108.40.206 directly, the website works, conclusion is that also the webserver works correctly. When I lookup the WHOIS data, all name servers and data are correctly. Yesterday I updated the name server details through our registrar, but that did not help.
Do you know what might be the problem here? I have never seen something like this before. The domains used here are the actual domains, so you can see for yourself.