porn DNS Report

Health Score: 72%

Need help fixing DNS ? Get an expert advise at support forum

Checked: 6 days before

Parent

NS records at parent servers

ns1.uniregistry.net [ 64.96.1.1 ]
ns2.uniregistry.info [ 64.96.245.53 ]
ns5.uniregistry.net [ 204.61.217.2 ]
ns6.uniregistry.info [ 206.51.254.2 ]
[These were obtained from a.root-servers.net]

Glue at parent nameservers 7/7

SUCCESS Parent nameservers know A records for your domain, Very good !

NS

Mismatched glue 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(ns1.uniregistry.net.	172800	IN	A	64.96.1.1) present at Parent, missing at (64.96.245.53)
(ns2.uniregistry.info.	172800	IN	A	64.96.245.53) present at Parent, missing at (64.96.245.53)
(ns5.uniregistry.net.	172800	IN	A	204.61.217.2) present at Parent, missing at (64.96.245.53)
(ns6.uniregistry.info.	172800	IN	A	206.51.254.2) present at Parent, missing at (64.96.245.53)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns6.uniregistry.info,ns5.uniregistry.net,ns2.uniregistry.info,ns1.uniregistry.net) at nameserver 64.96.245.53

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 0/10

Some nameservers does not respond:
2620:57:4000:1::1
2001:500:14:7002:ad::1
2620:171:804:ad2::2

Nameserver name validity 7/7

SUCCESS All of the NS records that your nameservers report are valid (no IPs or partial domain names).

Number of nameservers 5/5

SUCCESS You have 4 nameservers. You must have at least 2 nameservers (RFC2182 section 5 recommends at least 3 nameservers), and preferably no more than 7.

Lame nameservers 7/7

SUCCESS All the nameservers listed at the parent servers answer authoritatively for your domain.

Missing (stealth) nameservers 7/7

SUCCESS All your nameservers are also listed at the parent servers.

Root missing nameservers 7/7

SUCCESS All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers.

Nameservers on separate class C's 7/7

SUCCESS Nameservers are in a different networks.

public IPs 7/7

SUCCESS All of your NS records appear to use public IPs.

SOA

SOA record

SOA record is:
Hostmaster email
noc.afilias-nst.info
Serial
1000026673
Refresh
10800
Retry
3600
Expire
2764800
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 1000026673 That means that all your nameservers are using the same data.

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: a0.nic.porn, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 1000026673 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.

Refresh value 1/1

SUCCESS SOA Retry interval is : 10800 seconds. This seems OK. (Values 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.

Retry value 1/1

SUCCESS SOA Retry interval is : 3600 seconds. This seems OK. (Values 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.

Expire value 0/1

WARNING SOA Expire time is : 2764800 seconds. This seems too big;. (Values 604800 to 2419200 seconds (1-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.

TTL value 1/1

SUCCESS SOA Expire time is : 86400 seconds. This seems OK. (about 300 to 86400 seconds or 5 min - 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.

Info

DNS trace

Trace to porn
lookup porn at A.ROOT-SERVERS.NET(198.41.0.4) 68 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns2.uniregistry.info(64.96.245.53)
lookup porn at ns2.uniregistry.info(64.96.245.53) 10 ms
RECORD does not exist
Total time: 78 ms