meudesenvolvimentonogpa.com.br DNS Report

Health Score: 65%

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

Checked: 1 week before

Parent

NS records at parent servers

c.sec.dns.br [ 200.189.40.11 ]
b.sec.dns.br
[These were obtained from f.dns.br.]

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.
(b.sec.DNS.BR.		172800	IN	A	200.192.232.11) present at Parent, missing at (200.192.232.11)
(c.sec.dns.br.		172800	IN	A	200.189.40.11) present at Parent, missing at (200.192.232.11)

Nameservers A records 0/7

Some servers does not provide A records for nameservers.
missing A record(s) for (b.sec.dns.br,c.sec.dns.br) at nameserver 200.192.232.11

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:
2001:12f8:9:1::11

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
hostmaster.registro.br
Serial
2019268000
Refresh
345600
Retry
900
Expire
604800
TTL
3600

Serial agreement 7/7

SUCCESS All your nameservers agree that your SOA serial number is 2019268000 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: b.sec.dns.br That server is listed at the parent servers, which is correct.

Serial value 1/1

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

WARNING SOA Retry interval is : 345600 seconds. This seems too big;. (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 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 meudesenvolvimentonogpa.com.br
lookup meudesenvolvimentonogpa.com.br at A.ROOT-SERVERS.NET(198.41.0.4) 70 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.dns.br(200.219.148.10)
lookup meudesenvolvimentonogpa.com.br at a.dns.br(200.219.148.10) 127 ms
a.dns.br(200.219.148.10) refer to c.sec.dns.br(unknow IP)
extra IP lookup for c.sec.dns.br at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup c.sec.dns.br at A.ROOT-SERVERS.NET(198.41.0.4) 65 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to f.dns.br(200.219.159.10)
lookup c.sec.dns.br at f.dns.br(200.219.159.10) 66 ms
got A record 'c.sec.dns.br IN A 200.189.40.11' from c.sec.dns.br(200.219.159.10)
lookup meudesenvolvimentonogpa.com.br at c.sec.dns.br(200.189.40.11) 87 ms
got A record 'meudesenvolvimentonogpa.com.br IN A 108.168.214.227' from meudesenvolvimentonogpa.com.br(200.189.40.11)
Total time: 415 ms