DNS report for wwwapetube.com


ParentpassNS records at parent serversYour NS records at the parent servers are:

ns1.sedoparking.com. [ 91.195.240.162 ]
ns2.sedoparking.com. [ 91.195.241.162 ]
[These were obtained from h.gtld-servers.net.]
passGlue at parent nameserversParent nameservers (I checked with h.gtld-servers.net.) know A record for your domain, Very good !
NSinfoNS records at your nameserversYour NS records at your nameservers are:

At 91.195.240.162

At 91.195.241.162
passMismatched glueOK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
passNo NS A records at nameserversOK. Your nameservers do include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records.
failAll nameservers report identical NS recordsERROR. The NS records at all your nameservers are different, check the info above for details.
passAll nameservers respondOK. All of your nameservers listed at the parent nameservers responded.
passNameserver name validityOK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names).
passNumber of nameserversOK. You have 2 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.
passLame nameserversOK. All the nameservers listed at the parent servers answer authoritatively for your domain.
passMissing (stealth) nameserversOK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers.
failMissing nameservers 2ERROR: missing nameservers (nameservers what exist at root servers , but does not exist at your nameservers)
ns1.sedoparking.com. missing at ns1.sedoparking.com. [91.195.240.162]
ns2.sedoparking.com. missing at ns1.sedoparking.com. [91.195.240.162]
ns1.sedoparking.com. missing at ns2.sedoparking.com. [91.195.241.162]
ns2.sedoparking.com. missing at ns2.sedoparking.com. [91.195.241.162]
passNameservers on separate class C'sYour nameservers seems to be in different networks.
passAll NS IPs publicOK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays.
SOAinfoSOA recordYour SOA record is:
Primary nameserver: ns1.sedoparking.com.
Hostmaster E-mail address: hostmaster.sedo.de.
Serial #: 2014040101
Refresh: 86400
Retry: 10800
Expire: 604800
Default TTL:86400
passNS agreement on SOA Serial #OK. All your nameservers agree that your SOA serial number is 2014040101. That means that all your nameservers are using the same data.
passSOA MNAME CheckOK. Your SOA (Start of Authority) record states that your master (primary) name server is: ns1.sedoparking.com. That server is listed at the parent servers, which is correct.
passSOA Serial NumberOK. Your SOA serial number is: 2014040101. This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. This number must be incremented every time you make a DNS change.
warnSOA REFRESH valueYour SOA REFRESH interval is : 86400 seconds. This seems too long (about 3600-7200 seconds is good if not using DNS NOTIFY; RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours)). This value determines how often secondary/slave nameservers check with the master for updates.
warnSOA RETRY valueYour SOA RETRY interval is : 10800 seconds. This seems too long (about 120-7200 seconds is good). The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed.
passSOA EXPIRE valueYour SOA EXPIRE time is : 604800 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver.
passSOA MINIMUM TTL valueYour SOA MINIMUM TTL is : 86400 seconds. This seems normal (about 3,600 to 86400 seconds or 1-24 hours is good). RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.

Please, support us - set the link to thednsreport.com at your site or forum. Thank you!

Checked domains:
saggio.com.br webdesenvolvimento.com cjestrie.ca tubestac.com sentinelgold.co.uk wme.net mmfq.ipcam.hk dublinchiropodist.ie proyeweb.com elene.cn
Extra tool:
DNS timing lookup tool What is My IP page Check another domain FileKnow