Congratulation ! Domain atbrowncoaches.co.uk passed all DNS checkes,
To mark this on you site you can put the button
| Get button html source |
| Parent | pass | NS records at parent servers | Your NS records at the parent servers are: dns0.easily.co.uk. [ 212.53.77.27 ] dns1.easily.co.uk. [ 212.53.64.31 ] [These were obtained from ns2.nic.uk.] |
| pass | Glue at parent nameservers | Parent nameservers (I checked with ns2.nic.uk.) know A record for your domain, Very good ! | |
| NS | info | NS records at your nameservers | Your NS records at your nameservers are: dns0.easily.co.uk. [212.53.77.27 ] dns1.easily.co.uk. [212.53.64.31 ] |
| pass | Mismatched glue | OK. The DNS report did not detect any discrepancies between the glue provided by the parent servers and that provided by your authoritative DNS servers. | |
| pass | No NS A records at nameservers | OK. Your 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. | |
| pass | All nameservers report identical NS records | OK. The NS records at all your nameservers are identical. | |
| pass | All nameservers respond | OK. All of your nameservers listed at the parent nameservers responded. | |
| pass | Nameserver name validity | OK. All of the NS records that your nameservers report seem valid (no IPs or partial domain names). | |
| pass | Number of nameservers | OK. 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. | |
| pass | Lame nameservers | OK. All the nameservers listed at the parent servers answer authoritatively for your domain. | |
| pass | Missing (stealth) nameservers | OK. All 2 of your nameservers (as reported by your nameservers) are also listed at the parent servers. | |
| pass | Missing nameservers 2 | OK. All of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers. | |
| pass | Nameservers on separate class C's | Your nameservers seems to be in different networks. | |
| pass | All NS IPs public | OK. All of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays. | |
| SOA | info | SOA record | Your SOA record is: Primary nameserver: dns1.easily.co.uk. Hostmaster E-mail address: helpdesk.easily.co.uk. Serial #: 1306071200 Refresh: 3600 Retry: 604800 Expire: 86400 Default TTL:86400 |
| pass | NS agreement on SOA Serial # | OK. All your nameservers agree that your SOA serial number is 1306071200. That means that all your nameservers are using the same data. | |
| pass | SOA MNAME Check | OK. Your SOA (Start of Authority) record states that your master (primary) name server is: dns1.easily.co.uk. That server is listed at the parent servers, which is correct. | |
| pass | SOA Serial Number | OK. Your SOA serial number is: 1306071200. 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. | |
| pass | SOA REFRESH value | Your SOA REFRESH interval is : 3600 seconds. This seems normal (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. | |
| warn | SOA RETRY value | ERROR: SOA RETRY interval 604800 seconds more then SOA REFRESH interval which is 3600 seconds. | |
| warn | SOA EXPIRE value | Your SOA EXPIRE time is : 86400 seconds. This seems too small (about 1209600 to 2419200 seconds (2-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. | |
| pass | SOA MINIMUM TTL value | Your SOA MINIMUM TTL is : 86400 seconds. This seems normal (about 3,600 to 86400 seconds or 1-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. | |
Please, support us - set the link to thednsreport.com at your site or forum. Thank you!
phillipsedison.com pc10directory.info racheldvr.dyndns.org realcouplecam.com tam1sesli.com sinapse.ind.br bstnet.com.br ayakkabimakine.net sibername.com ucommerce.com.br
Extra tool:
DNS timing lookup tool What is My IP page Check another domain One click file upload service URL Shortener FileKnow