Re: Relevant RFC on A records for NS's

2009-04-30 Thread Scott Haneda
On Apr 30, 2009, at 3:54 AM, Kal Feher wrote: Lets check where they are delegated: 1st the hostwizard domain $ dig ns hostwizard.com +short ns1.hostwizard.com. ns1.nacio.com. Now nacio $ dig ns nacio.com +short ns1.nacio.com. ns3.nacio.com. ns2.nacio.com. So what _should_ we see if I query ns1

Re: Relevant RFC on A records for NS's

2009-04-30 Thread Scott Haneda
On Apr 30, 2009, at 2:44 AM, Noel Butler wrote: On Thu, 2009-04-30 at 19:38, Scott Haneda wrote: On Apr 30, 2009, at 1:43 AM, Kal Feher wrote: > When I clicked on that link the only error was an MNAME error. Did > you see > another error? (I wonder if it was a transient error you observed, >

Re: Relevant RFC on A records for NS's

2009-04-30 Thread Kal Feher
Firstly I should say that I agree with those who think the tool is a little suspect in its efficacy. I tried a few domains under some cctlds and it appears as if the code assumes only GTLDs. Nevertheless, it may be instructive to describe what you saw Scott. You have 2 name servers: $ dig ns newge

Re: Relevant RFC on A records for NS's

2009-04-30 Thread Sten Carlsen
I get the same error when checking my own domain. A check with dig results in proving that the tool is wrong. Scott Haneda wrote: > On Apr 30, 2009, at 1:43 AM, Kal Feher wrote: > >> When I clicked on that link the only error was an MNAME error. Did >> you see >> another error? (I wonder if it was

Re: Relevant RFC on A records for NS's

2009-04-30 Thread Noel Butler
On Thu, 2009-04-30 at 19:38, Scott Haneda wrote: > On Apr 30, 2009, at 1:43 AM, Kal Feher wrote: > > > When I clicked on that link the only error was an MNAME error. Did > > you see > > another error? (I wonder if it was a transient error you observed, > > because > > it appears different to

Re: Relevant RFC on A records for NS's

2009-04-30 Thread Scott Haneda
On Apr 30, 2009, at 1:43 AM, Kal Feher wrote: When I clicked on that link the only error was an MNAME error. Did you see another error? (I wonder if it was a transient error you observed, because it appears different to yours). The error according to the report (run against isc.org): "ERROR

Re: Relevant RFC on A records for NS's

2009-04-30 Thread Kal Feher
When I clicked on that link the only error was an MNAME error. Did you see another error? (I wonder if it was a transient error you observed, because it appears different to yours). The error according to the report (run against isc.org): "ERROR: Your SOA (Start of Authority) record states that yo

Relevant RFC on A records for NS's

2009-04-30 Thread Scott Haneda
Someone pointed me to this http://thednsreport.com/?domain=isc.org I am not a huge fan of these checking tools, this one has me curious. My domain of course has the same error, which is a little comforting, sine I am in good company :) What is this error asking of me, they are wanting in my c