 |
Missing nameservers reported by parent |
FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
ns316.mylittledatacenter.com
ns315.mylittledatacenter.com |
|
Missing nameservers reported by your nameservers |
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:
ns425.mihanwebhost.com
ns426.mihanwebhost.com
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). |
 |
Domain CNAMEs |
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. |
|
NSs CNAME check |
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. |
 |
Different subnets |
WARNING: Not all of your nameservers are in different subnets |
|
IPs of nameservers are public |
Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like |
|
DNS servers allow TCP connection |
OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default. |
|
Different autonomous systems |
WARNING: Single point of failure |
|
Stealth NS records sent |
Stealth NS records were sent:
ns316.mylittledatacenter.com
ns315.mylittledatacenter.com |
پاسخ : مشکل در ست کردن dns های سایت |رفع خطای DNS
پاسخ با نقل قول