SUCCESS
Parent nameservers know A records for your domain, Very good !
NS
Mismatched glue
7/7
SUCCESS
The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers.
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
noc.ht-systems.ru
Serial
2019061172
Refresh
36000
Retry
300
Expire
604800
TTL
1800
Serial agreement
7/7
SUCCESS
All your nameservers agree that your SOA serial number is 2019061172 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: ns1.ht-systems.ru That server is listed at the parent servers, which is correct.
Serial value
1/1
SUCCESS
SOA serial number is: 2019061172 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 : 36000 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 : 300 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 : 604800 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 : 1800 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 brlic.ru
lookup brlic.ru at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup brlic.ru at a.dns.ripn.net(193.232.128.6) 115 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.ht-systems.RU(unknow IP)
extra IP lookup for ns1.ht-systems.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.ht-systems.RU at A.ROOT-SERVERS.NET(198.41.0.4) 36 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns1.ht-systems.RU at a.dns.ripn.net(193.232.128.6) 114 ms
a.dns.ripn.net(193.232.128.6) refer to ns2.ht-systems.RU(unknow IP)
extra IP lookup for ns2.ht-systems.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns2.ht-systems.RU at A.ROOT-SERVERS.NET(198.41.0.4) 37 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns2.ht-systems.RU at a.dns.ripn.net(193.232.128.6) 116 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.ht-systems.RU(unknow IP)
extra IP lookup for ns1.ht-systems.RU at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup ns1.ht-systems.RU at A.ROOT-SERVERS.NET(198.41.0.4) 38 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup ns1.ht-systems.RU at a.dns.ripn.net(193.232.128.6) 116 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.ht-systems.RU(78.110.50.60)
lookup ns1.ht-systems.RU at ns1.ht-systems.RU(78.110.50.60) 116 ms
got A record 'ns1.ht-systems.RU IN A 78.110.50.60' from ns1.ht-systems.RU(78.110.50.60)
lookup ns2.ht-systems.RU at ns1.ht-systems.RU(78.110.50.60) 115 ms
got A record 'ns2.ht-systems.RU IN A 95.163.104.106' from ns2.ht-systems.RU(78.110.50.60)
lookup ns1.ht-systems.RU at ns2.ht-systems.RU(95.163.104.106) 120 ms
got A record 'ns1.ht-systems.RU IN A 78.110.50.60' from ns1.ht-systems.RU(95.163.104.106)
lookup brlic.ru at ns1.ht-systems.RU(78.110.50.60) 115 ms
got A record 'brlic.ru IN A 78.110.50.152' from brlic.ru(78.110.50.60)