Need help fixing DNS ? Get an expert advise at
support forum
Checked: 1 month before
Parent
NS records at parent servers
ns210.axc.nl
ns209.axc.nl
ns3.fwh1.nl
[These were obtained from ns3.dns.nl.]
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 axc.nlCheck fwh1.nl
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
0/10
Some nameservers does not respond:
ns3.fwh1.nl.
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 3 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.sfm-web.nl.
ns1.sfm-web.nl.
Root missing nameservers
0/7
DANGER
There are nameservers not listed at your nameservers:
ns210.axc.nl.
ns209.axc.nl.
ns3.fwh1.nl.
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
hostmaster.sfm-web.nl
Serial
2017070721
Refresh
14400
Retry
3600
Expire
1209600
TTL
14400
Serial agreement
7/7
SUCCESS
All your nameservers agree that your SOA serial number is 2017070721 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: ns1.sfm-web.nl, but that server is not listed at the parent servers.
Serial value
1/1
SUCCESS
SOA serial number is: 2017070721 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 : 14400 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 : 14400 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 sfm-web.nl
lookup sfm-web.nl at A.ROOT-SERVERS.NET(198.41.0.4) 19 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns3.dns.nl(194.171.17.10)
lookup sfm-web.nl at ns3.dns.nl(194.171.17.10) 93 ms
ns3.dns.nl(194.171.17.10) refer to ns210.axc.nl(unknow IP)
extra IP lookup for ns210.axc.nl at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns210.axc.nl at A.ROOT-SERVERS.NET(198.41.0.4) 11 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to ns1.dns.nl(193.176.144.5)
lookup ns210.axc.nl at ns1.dns.nl(193.176.144.5) 93 ms
ns1.dns.nl(193.176.144.5) refer to nsi2.axc.nl(138.68.172.80)
lookup ns210.axc.nl at nsi2.axc.nl(138.68.172.80) 74 ms
got A record 'ns210.axc.nl IN A 185.175.200.185' from ns210.axc.nl(138.68.172.80)
lookup sfm-web.nl at ns210.axc.nl(185.175.200.185) 92 ms
got A record 'sfm-web.nl IN A 185.182.56.152' from sfm-web.nl(185.175.200.185)