musician.org DNS Report

Health Score: 57%

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

Checked: 1 week before

Parent

NS records at parent servers

pdns3.ultradns.org [ 199.7.68.1 ]
pdns4.ultradns.org [ 199.7.69.1 ]
pdns1.ultradns.net
pdns2.ultradns.net
[These were obtained from a0.org.afilias-nst.info.]

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 0/7

The glue provided by the root servers does not match glue that provided by your authoritative DNS servers.
(pdns3.ultradns.org.	86400	IN	A	199.7.68.1) present at Parent, missing at (204.74.108.1, 204.74.109.1)
(pdns4.ultradns.org.	86400	IN	A	199.7.69.1) present at Parent, missing at (204.74.108.1, 204.74.109.1)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (pdns1.ultradns.net,pdns2.ultradns.net,pdns3.ultradns.org,pdns4.ultradns.org,pdns5.ultradns.info,pdns6.ultradns.co.uk) at nameserver 204.74.108.1
missing A record(s) for (pdns1.ultradns.net,pdns2.ultradns.net,pdns3.ultradns.org,pdns4.ultradns.org,pdns5.ultradns.info,pdns6.ultradns.co.uk) at nameserver 204.74.109.1

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:
2610:a1:1015::1
2001:502:4612::1

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 0/7

DANGER There are nameservers not listed at the parent servers:
pdns5.ultradns.info.
pdns6.ultradns.co.uk.

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
ggorman.easylink.com
Serial
2014091513
Refresh
10800
Retry
3600
Expire
2592000
TTL
360000

Serial agreement 7/7

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

Serial value 1/1

SUCCESS SOA serial number is: 2014091513 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 : 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 0/1

WARNING SOA Expire time is : 360000 seconds. This seems too big;. (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 musician.org
lookup musician.org at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to d0.org.afilias-nst.org(199.19.57.1)
lookup musician.org at d0.org.afilias-nst.org(199.19.57.1) 3 ms
d0.org.afilias-nst.org(199.19.57.1) refer to pdns3.ultradns.org(199.7.68.1)
lookup musician.org at pdns3.ultradns.org(199.7.68.1) 9 ms
got A record 'musician.org IN A 204.74.99.100' from musician.org(199.7.68.1)
Total time: 23 ms