On 01/09/2013 10:24, Grant wrote: >> Instead just use dig, using google.com as an example get the NS records >> > first: >> > >> > $ dig ns google.com +short >> > ns3.google.com. >> > ns2.google.com. >> > ns1.google.com. >> > ns4.google.com. >> > >> > Then query each of those name server in turn directly for the SOA: >> > >> > $ dig soa google.com +short @ns3.google.com >> > ns1.google.com. dns-admin.google.com. 2013081400 7200 1800 1209600 300 >> > >> > That's a correct SOA record. > Does this look OK? > > $ dig soa MASKED.com +short @MASKED1.MASKED.com > MASKED1.MASKED.com. MASKED.MASKED.com. YYYYMMDD00 3600 1801 604800 3601
That looks OK, doubly so if all listed NS servers return the same answer In all likelihood I'd say you are dealing with a DNS-check web site that is over-enthusiastic, or can't deal with network errors or just plain buggy. IOW, odds are very good that there is nothing wrong with your domain at all :-) -- Alan McKinnon alan.mckin...@gmail.com
