lovecity3d.net DNS Report

Health Score: 86%

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

Checked: 6 days before

Parent

NS records at parent servers

dns1.zenon.net [ 62.113.104.4 ]
dns2.zenon.net [ 195.2.83.38 ]
[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.
(dns1.zenon.net.		600	IN	A	195.2.64.38) present at (62.113.104.4, 195.2.83.38), missing at Parent
(dns1.zenon.net.		600	IN	A	62.113.107.4) present at (62.113.104.4, 195.2.83.38), missing at Parent
(dns2.zenon.net.		600	IN	A	62.113.106.4) present at (62.113.104.4, 195.2.83.38), missing at Parent
(dns2.zenon.net.		600	IN	A	62.113.105.4) present at (62.113.104.4, 195.2.83.38), missing at Parent

Nameservers A records 7/7

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

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 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
dnsmaster.zenon.net
Serial
142826917
Refresh
7200
Retry
3600
Expire
1209600
TTL
300

Serial agreement 7/7

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

Serial value 0/1

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

SUCCESS SOA Expire time is : 1209600 seconds. This seems OK. (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 : 300 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 lovecity3d.net
lookup lovecity3d.net at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup lovecity3d.net at a.gtld-servers.net(192.5.6.30) 3 ms
a.gtld-servers.net(192.5.6.30) refer to dns1.zenon.net(62.113.104.4)
lookup lovecity3d.net at dns1.zenon.net(62.113.104.4) 118 ms
got A record 'lovecity3d.net IN A 213.189.196.125' from lovecity3d.net(62.113.104.4)
Total time: 129 ms