antiporno.org DNS Report

Health Score: 62%

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

Checked: 1 week before

Parent

NS records at parent servers

dns1.yandex.ru
dns2.yandex.ru
[These were obtained from d0.org.afilias-nst.org.]

Glue at parent nameservers 0/7

WARNING The parent servers are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records. That may cause some extra milliseconds in DNS. This will usually occur if your DNS servers are not in the same TLD as your domain

NS

Mismatched glue 7/7

Skip glue checking. Make sure the nameservers domain is good standing Check yandex.ru

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (dns2.yandex.net,dns1.yandex.net) at nameserver 213.180.204.213
missing A record(s) for (dns2.yandex.net,dns1.yandex.net) at nameserver 93.158.134.213

Nameservers report identical NS records 7/7

SUCCESS The NS records at all your nameservers are identical.

Nameservers respond 10/10

SUCCESS All of your nameservers listed at the parent nameservers responded.

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 2/5

WARNING 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.

Lame nameservers 7/7

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

Missing (stealth) nameservers 0/7

DANGER There are nameservers not listed at the parent servers:
dns2.yandex.net.
dns1.yandex.net.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
dns1.yandex.ru.
dns2.yandex.ru.

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
dns-hosting.yandex.ru
Serial
1
Refresh
900
Retry
90
Expire
86400
TTL
900

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 1 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: dns1.yandex.net, but that server is not listed at the parent servers.

Serial value 0/1

WARNING SOA serial number is: 1 This not 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 0/1

WARNING SOA Retry interval is : 900 seconds. This seems too small. (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 0/1

WARNING SOA Retry interval is : 90 seconds. This seems too small. (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 : 86400 seconds. This seems too small. (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 : 900 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 antiporno.org
lookup antiporno.org at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d0.org.afilias-nst.org(199.19.57.1)
lookup antiporno.org at d0.org.afilias-nst.org(199.19.57.1) 64 ms
d0.org.afilias-nst.org(199.19.57.1) refer to dns1.yandex.ru(unknow IP)
extra IP lookup for dns1.yandex.ru at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup dns1.yandex.ru at A.ROOT-SERVERS.NET(198.41.0.4) 38 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup dns1.yandex.ru at a.dns.ripn.net(193.232.128.6) 117 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 117 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 117 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 117 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.yandex.RU(unknow IP)
extra IP lookup for ns2.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.yandex.RU at a.dns.ripn.net(193.232.128.6) 118 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.yandex.RU(unknow IP)
extra IP lookup for ns1.yandex.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.yandex.RU at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns1.yandex.RU at a.dns.ripn.net(193.232.128.6) 118 ms
a.dns.ripn.net(193.232.128.6) refer to ns9.z5h64q92x9.net(unknow IP)
extra IP lookup for ns9.z5h64q92x9.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns9.z5h64q92x9.net at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup ns9.z5h64q92x9.net at a.gtld-servers.net(192.5.6.30) 37 ms
a.gtld-servers.net(192.5.6.30) refer to ns2.yandex.net(93.158.134.1)
lookup ns9.z5h64q92x9.net at ns2.yandex.net(93.158.134.1) 112 ms
got A record 'ns9.z5h64q92x9.net IN A 80.239.201.9' from ns9.z5h64q92x9.net(93.158.134.1)
lookup ns1.yandex.RU at ns9.z5h64q92x9.net(80.239.201.9) 135 ms
lookup ns2.yandex.RU at ns1.yandex.RU() 130 ms
lookup ns2.yandex.RU at ns2.yandex.RU() 130 ms
lookup ns2.yandex.RU at ns2.yandex.RU() 135 ms
lookup ns2.yandex.RU at ns2.yandex.RU() 134 ms
lookup dns1.yandex.ru at ns2.yandex.RU() 131 ms
got A record 'dns1.yandex.ru IN A 213.180.204.213' from dns1.yandex.ru()
lookup antiporno.org at dns1.yandex.ru(213.180.204.213) 136 ms
got A record 'antiporno.org IN A 185.12.95.222' from antiporno.org(213.180.204.213)
Total time: 2139 ms