level3.net DNS Report

Health Score: 58%

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

Checked: 2 years before

Parent

NS records at parent servers

ns1.l3.net [ 209.244.0.1 ]
ns2.l3.net [ 209.244.0.2 ]
[These were obtained from e.gtld-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.l3.net.		172800	IN	A	209.244.0.1) present at Parent, missing at (209.244.0.1, 209.244.0.2)
(ns2.l3.net.		172800	IN	A	209.244.0.2) present at Parent, missing at (209.244.0.1, 209.244.0.2)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns2.Level3.net,ns1.Level3.net) at nameserver 209.244.0.1
missing A record(s) for (ns1.Level3.net,ns2.Level3.net) at nameserver 209.244.0.2

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:
ns2.level3.net.
ns1.level3.net.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
ns1.l3.net.
ns2.l3.net.

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.level3.net
Serial
2017071902
Refresh
7200
Retry
600
Expire
2592000
TTL
3600

Serial agreement 0/7

DANGER Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
There is serial 2017071902 at nameserver(s) (209.244.0.1)
There is serial 2017071702 at nameserver(s) (209.244.0.2)

SOA MNAME 0/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2017071902 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 : 7200 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 : 600 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 : 2592000 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 : 3600 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 level3.net
lookup level3.net at A.ROOT-SERVERS.NET(198.41.0.4) 5 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup level3.net at e.gtld-servers.net(192.12.94.30) 10 ms
e.gtld-servers.net(192.12.94.30) refer to ns1.l3.net(209.244.0.1)
lookup level3.net at ns1.l3.net(209.244.0.1) 2 ms
Total time: 17 ms