DNS Lookup and Diagnostics Tool
Get a dns lookup and status report on any website
DNS Results for: shop4korea.com
generated at 2015-04-26 12:06:48 -0500 (click 'Report' for realtime info)
Use the DNS Lookup Tool to get a report on a site's dns configuration. Webmasters can use this tool to assist in troubleshooting dns configurations.
Simply enter a url in the text box and click the 'Report' button to get a detailed, realtime report on a site's dns configuration.
|Parent||Domain NS records||Nameserver records returned by the parent servers are:
ns1.dreamhost.com ['188.8.131.52'] [TTL=172800]
ns2.dreamhost.com ['184.108.40.206'] [TTL=172800]
ns3.dreamhost.com ['220.127.116.11'] [TTL=172800]
m.gtld-servers.net. was kind enough to give us that information.
|TLD Parent Check||Good. m.gtld-servers.net., the parent server I interrogated, has information for your TLD.|
|Your nameservers are listed||Good. The parent server m.gtld-servers.net. has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.|
|DNS Parent sent Glue||Good The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3)|
|Nameservers A records||Good. Every nameserver listed has A records. This is a must if you want to be found.|
|NS||NS records from your nameservers||NS records got from your nameservers listed at the parent NS are:
Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly.
|Recursive Queries||Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.|
|Same Glue||Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers|
|Glue for NS records||OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors!|
|Mismatched NS records||OK. The NS records at all your nameservers are identical.|
|DNS servers responded||Good. All nameservers listed at the parent server responded.|
|Name of nameservers are valid||OK. All of the NS records that your nameservers report seem valid.|
|Multiple Nameservers||Good. You have multiple nameserversAccording to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.|
|Nameservers are lame||
Following nameservers listed at the parent servers does not answer authoritatively for your domain.
|Missing nameservers reported by parent||OK. All NS records are the same at the parent and at your nameservers.|
|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:
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||OK. Looks like you have nameservers on 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||OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.|
|Stealth NS records sent||Ok. No stealth ns records are sent|
|SOA||SOA record||No valid SOA record came back!|
|MX||MX Records||Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!|
|WWW||WWW A Record||
Your www.shop4korea.com A record is:
|IPs are public||OK. All of your WWW IPs appear to be public IPs.|
|WWW CNAME||OK. No CNAME|