dpcnet.com.br DNS Report

Health Score: 54%

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

Checked: 5 months before

Parent

NS records at parent servers

alpha2.dpcnet.com.br [ 45.70.32.18 ]
ns2.signet.com.br [ 138.121.55.247 ]
ns1.signet.com.br [ 138.121.55.252 ]
alpha1.dpcnet.com.br [ 138.121.52.30 ]
[These were obtained from f.dns.br.]

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.
(ns1.signet.com.br.	3600	IN	A	138.121.55.252) present at Parent, missing at (45.70.32.18, 138.121.55.247, 138.121.55.252, 138.121.52.30)
(ns2.signet.com.br.	3600	IN	A	138.121.55.247) present at Parent, missing at (45.70.32.18, 138.121.55.247, 138.121.55.252, 138.121.52.30)
(alpha2.dpcnet.com.br.	3600	IN	A	45.70.32.18) present at Parent, missing at (45.70.32.18, 138.121.55.247, 138.121.55.252, 138.121.52.30)
(alpha1.dpcnet.com.br.	3600	IN	A	138.121.52.30) present at Parent, missing at (138.121.55.247, 138.121.55.252)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (ns1.signet.com.br,ns2.signet.com.br) at nameserver 45.70.32.18
missing A record(s) for (ns2.signet.com.br,ns1.signet.com.br) at nameserver 138.121.52.30

Nameservers report identical NS records 0/7

The NS records at your nameservers are different
At (45.70.32.18 138.121.52.30) there are nameservers: ns1.signet.com.br. alpha1.dpcnet.com.br. ns2.signet.com.br.
At (138.121.55.247 138.121.55.252) there are nameservers:

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 0/7

Lame nameservers:
138.121.55.247
138.121.55.252

Missing (stealth) nameservers 7/7

SUCCESS All your nameservers are also listed at the parent servers.

Root missing nameservers 0/7

DANGER There are nameservers not listed at your nameservers:
alpha2.dpcnet.com.br.

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
leonardo.dpcnet.com.br
Serial
2018070302
Refresh
3600
Retry
900
Expire
86400
TTL
43200

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 2018070302 at nameserver(s) (45.70.32.18 138.121.52.30)
There is serial at nameserver(s) (138.121.55.247 138.121.55.252)

SOA MNAME 0/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2018070302 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 : 3600 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 : 900 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 0/1

WARNING SOA Expire time is : 86400 seconds. This seems too small. (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 : 43200 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 dpcnet.com.br
lookup dpcnet.com.br at A.ROOT-SERVERS.NET(198.41.0.4) 13 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.br(200.160.0.10)
lookup dpcnet.com.br at a.dns.br(200.160.0.10) 116 ms
a.dns.br(200.160.0.10) refer to alpha1.dpcnet.com.br(138.121.52.30)
lookup dpcnet.com.br at alpha1.dpcnet.com.br(138.121.52.30) 133 ms
got A record 'dpcnet.com.br IN A 138.121.52.30' from dpcnet.com.br(138.121.52.30)
Total time: 262 ms