Need help fixing DNS ? Get an expert advise at
support forum
Checked: 2 months before
Parent
NS records at parent servers
temmdns1.optele.net
temmdns2.optele.net
[These were obtained from o.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
7/7
Skip glue checking. Make sure the nameservers domain is good standing
Check optele.net
Nameservers A records
0/7
Some servers does not provide A records for nameservers.
missing A record(s) for (temmdns2.optele.net,temmdns1.optele.net) at nameserver 200.76.80.20
missing A record(s) for (temmdns1.optele.net,temmdns2.optele.net) at nameserver 200.76.88.22
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
root.temmdns1.optele.net
Serial
2014061706
Refresh
10800
Retry
3600
Expire
604800
TTL
10800
Serial agreement
7/7
SUCCESS
All your nameservers agree that your SOA serial number is 2014061706 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: temmdns1.optele.net That server is listed at the parent servers, which is correct.
Serial value
1/1
SUCCESS
SOA serial number is: 2014061706 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 : 10800 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 odmexpress.com.mx
lookup odmexpress.com.mx at A.ROOT-SERVERS.NET(198.41.0.4) 8 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to o.mx-ns.mx(200.23.1.1)
lookup odmexpress.com.mx at o.mx-ns.mx(200.23.1.1) 85 ms
o.mx-ns.mx(200.23.1.1) refer to temmdns2.optele.net(unknow IP)
extra IP lookup for temmdns2.optele.net at root server A.ROOT-SERVERS.NET(198.41.0.4)
lookup temmdns2.optele.net at A.ROOT-SERVERS.NET(198.41.0.4) 10 ms
A.ROOT-SERVERS.NET(198.41.0.4) refer to a.gtld-servers.net(192.5.6.30)
lookup temmdns2.optele.net at a.gtld-servers.net(192.5.6.30) 20 ms
a.gtld-servers.net(192.5.6.30) refer to temmdns2.optele.net(200.76.88.22)
lookup temmdns2.optele.net at temmdns2.optele.net(200.76.88.22) 69 ms
got A record 'temmdns2.optele.net IN A 200.76.88.22' from temmdns2.optele.net(200.76.88.22)
lookup odmexpress.com.mx at temmdns2.optele.net(200.76.88.22) 73 ms
got A record 'odmexpress.com.mx IN A 200.36.176.149' from odmexpress.com.mx(200.76.88.22)