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

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

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):

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 yours).

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 a

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,