fcirkutsk.ru DNS Report

Health Score: 62%

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

Checked: 1 month before

Parent

NS records at parent servers

ns1.firstvds.ru [ 82.146.43.2 ]
ns2.firstvds.ru [ 94.250.248.160 ]
dns1.yandex.net
dns2.yandex.net
[These were obtained from a.dns.ripn.net.]

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.
(ns1.firstvds.ru.		345600	IN	A	82.146.43.2) present at Parent, missing at (213.180.204.213, 93.158.134.213)
(ns2.firstvds.ru.		345600	IN	A	94.250.248.160) present at Parent, missing at (213.180.204.213, 93.158.134.213)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (dns2.yandex.net,dns1.yandex.net) at nameserver 82.146.43.2
missing A record(s) for (dns2.yandex.net,dns1.yandex.net) at nameserver 94.250.248.160
missing A record(s) for (dns2.yandex.net,dns1.yandex.net) at nameserver 213.180.204.213
missing A record(s) for (dns2.yandex.net,dns1.yandex.net) at nameserver 93.158.134.213

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (82.146.43.2 94.250.248.160) there are nameservers: dns2.yandex.net. ns1.firstvds.ru. ns2.firstvds.ru. dns1.yandex.net.
At (213.180.204.213 93.158.134.213) there are nameservers: dns2.yandex.net. dns1.yandex.net.

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 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 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
root.fcirkutsk.ru
Serial
2019020606
Refresh
10800
Retry
3600
Expire
604800
TTL
3600

Serial agreement 0/7

DANGER Some nameservers have a different soa serial number That can occur because of recent master update (slave have not loaded master zone yet) or the is a problem in DNS.
There is serial 2019020606 at nameserver(s) (82.146.43.2 94.250.248.160)
There is serial 1 at nameserver(s) (213.180.204.213 93.158.134.213)

SOA MNAME 0/3

DANGER SOA (Start of Authority) record states that your master (primary) name server is: fcirkutsk.ru, but that server is not listed at the parent servers.

Serial value 1/1

SUCCESS SOA serial number is: 2019020606 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 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 : 3600 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 fcirkutsk.ru
lookup fcirkutsk.ru at A.ROOT-SERVERS.NET(198.41.0.4) 41 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.ripn.net(193.232.128.6)
lookup fcirkutsk.ru at a.dns.ripn.net(193.232.128.6) 114 ms
a.dns.ripn.net(193.232.128.6) refer to ns1.firstvds.ru(82.146.43.2)
lookup fcirkutsk.ru at ns1.firstvds.ru(82.146.43.2) 117 ms
got A record 'fcirkutsk.ru IN A 149.154.66.250' from fcirkutsk.ru(82.146.43.2)
Total time: 272 ms