congresogto.gob.mx DNS Report

Health Score: 62%

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

Checked: 2 weeks before

Parent

NS records at parent servers

ns1.bdm.microsoftonline.com
dns.congresogto.gob.mx [ 200.36.54.227 ]
[These were obtained from c.mx-ns.mx.]

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.
(dns.congresogto.gob.mx.	86400	IN	A	200.36.54.227) present at Parent, missing at (207.46.15.59)
(ns1.bdm.microsoftonline.com.	86400	IN	A	207.46.15.59) present at (207.46.15.59), missing at Parent
(ns2.bdm.microsoftonline.com.	86400	IN	A	157.56.81.41) present at (207.46.15.59), missing at Parent
(ns3.bdm.microsoftonline.com.	86400	IN	A	191.232.83.138) present at (207.46.15.59), missing at Parent
(ns4.bdm.microsoftonline.com.	86400	IN	A	13.106.220.9) present at (207.46.15.59), missing at Parent
(ns1.bdm.microsoftonline.com.	3600	IN	A	207.46.15.59) present at (200.36.54.227), missing at Parent
(ns2.bdm.microsoftonline.com.	3600	IN	A	157.56.81.41) present at (200.36.54.227), missing at Parent
(ns3.bdm.microsoftonline.com.	3600	IN	A	191.232.83.138) present at (200.36.54.227), missing at Parent
(ns4.bdm.microsoftonline.com.	3600	IN	A	157.55.45.9) present at (200.36.54.227), missing at Parent

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

The NS records at your nameservers are different
At (207.46.15.59) there are nameservers: ns1.bdm.microsoftonline.com. ns2.bdm.microsoftonline.com. ns3.bdm.microsoftonline.com. ns4.bdm.microsoftonline.com.
At (200.36.54.227) there are nameservers: ns1.bdm.microsoftonline.com. dns.congresogto.gob.mx. ns2.bdm.microsoftonline.com. ns3.bdm.microsoftonline.com. ns4.bdm.microsoftonline.com.

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

DANGER There are nameservers not listed at the parent servers:
ns2.bdm.microsoftonline.com.
ns3.bdm.microsoftonline.com.
ns4.bdm.microsoftonline.com.

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
msnhst.microsoft.com
Serial
2007070100
Refresh
10800
Retry
1800
Expire
691200
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 2007070100 at nameserver(s) (207.46.15.59)
There is serial 2011120467 at nameserver(s) (200.36.54.227)

SOA MNAME 3/3

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

Serial value 1/1

SUCCESS SOA serial number is: 2007070100 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 : 1800 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 : 691200 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 congresogto.gob.mx
lookup congresogto.gob.mx at A.ROOT-SERVERS.NET(198.41.0.4) 24 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to o.mx-ns.mx(200.23.1.1)
lookup congresogto.gob.mx at o.mx-ns.mx(200.23.1.1) 100 ms
o.mx-ns.mx(200.23.1.1) refer to dns.congresogto.gob.mx(200.36.54.227)
lookup congresogto.gob.mx at dns.congresogto.gob.mx(200.36.54.227) 104 ms
got A record 'congresogto.gob.mx IN A 199.201.88.135' from congresogto.gob.mx(200.36.54.227)
Total time: 228 ms