remote-work.pro DNS Report

Health Score: 90%

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

Checked: 1 week before

Parent

NS records at parent servers

ns1069.ifastnet.com
ns2069.ifastnet.com
[These were obtained from b0.pro.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 ifastnet.com

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
response.ifastnet.com
Serial
2019112104
Refresh
3660
Retry
951
Expire
604810
TTL
86400

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2019112104 That means that all your nameservers are using the same data.

SOA MNAME 3/3

SUCCESS SOA (Start of Authority) record states that your master (primary) name server is: ns1069.ifastnet.com That server is listed at the parent servers, which is correct.

Serial value 1/1

SUCCESS SOA serial number is: 2019112104 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 : 3660 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 : 951 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 : 604810 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 : 86400 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 remote-work.pro
lookup remote-work.pro at A.ROOT-SERVERS.NET(198.41.0.4) 43 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to b0.pro.afilias-nst.org(199.182.1.1)
lookup remote-work.pro at b0.pro.afilias-nst.org(199.182.1.1) 73 ms
b0.pro.afilias-nst.org(199.182.1.1) refer to ns2069.ifastnet.com(unknow IP)
extra IP lookup for ns2069.ifastnet.com at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2069.ifastnet.com at A.ROOT-SERVERS.NET(198.41.0.4) 43 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to e.gtld-servers.net(192.12.94.30)
lookup ns2069.ifastnet.com at e.gtld-servers.net(192.12.94.30) 20 ms
e.gtld-servers.net(192.12.94.30) refer to ns2.ifastnet.org(unknow IP)
extra IP lookup for ns2.ifastnet.org at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.ifastnet.org at A.ROOT-SERVERS.NET(198.41.0.4) 43 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a0.org.afilias-nst.info(199.19.56.1)
lookup ns2.ifastnet.org at a0.org.afilias-nst.info(199.19.56.1) 149 ms
a0.org.afilias-nst.info(199.19.56.1) refer to ns1.byethost.org(31.22.4.231)
lookup ns2.ifastnet.org at ns1.byethost.org(31.22.4.231) 80 ms
got A record 'ns2.ifastnet.org IN A 31.22.4.21' from ns2.ifastnet.org(31.22.4.231)
lookup ns2069.ifastnet.com at ns2.ifastnet.org(31.22.4.21) 79 ms
got A record 'ns2069.ifastnet.com IN A 185.2.168.12' from ns2069.ifastnet.com(31.22.4.21)
lookup remote-work.pro at ns2069.ifastnet.com(185.2.168.12) 79 ms
got A record 'remote-work.pro IN A 185.2.168.12' from remote-work.pro(185.2.168.12)
Total time: 609 ms