Question:
Difficult DNS problem I cannot identify?
Sciman
2006-07-04 15:36:55 UTC
Hi, daily I have problems seeing my site http://prchive.net. A friend in India does at times. However, I can do a 200 header check from other servers and it checks out ok. Also, other people can see the site. Can anyone explain what might be happening as the server checks out fine and displays http://prchive.net all the time with tech support where they are located. The nameservers I use are ns1.dillweb.com and ns2.dillweb.com. Thanks for any insight.
Three answers:
DC
2006-07-04 16:03:25 UTC
ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are:

Server 66.111.249.84 reports that it will do recursive lookups. [test]

Server 66.111.249.85 reports that it will do recursive lookups. [test]





See this page for info on closing open DNS servers.



Missing (stealth) nameservers FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNS Report will not query these servers, so you need to be very careful that they are working properly.



ns2.webhostplus.net.ns1.webhostplus.net.

This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).

FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:

ns1.dillweb.com.

ns2.dillweb.com.
duct_tape_is_good
2006-07-04 15:52:52 UTC
take a look at http://www.dollardns.net/cgi-bin/nstrace/index.pl



also, (if you're using windows xp) do start > run > cmd > tracert domain/ip address.

on unix/linux, traceroute domain/ip address

another useful *nix tool is "dig"



find out if something is null routing and where it is failing.



there could be a couple other problems if you are serving from your home network that i dont feel like getting into.



if you have a dynamic ip address, make sure you don't have p[roblems with your cache (on windows, ipconfig /flushdns will flush your dns) flushing the cache on *nix is a but more indepth, and depends on the os at times.



look on google.com
anonymous
2006-07-04 15:41:32 UTC
Do you run through a rotuer? Could be the DNS on the router.


This content was originally posted on Y! Answers, a Q&A website that shut down in 2021.
Loading...