Relevant RFC on A records for NS's

Scott Haneda talklists at
Thu Apr 30 09:38:37 UTC 2009

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
> "ERROR: Your SOA (Start of Authority) record states that your master
> (primary) name server is: That server is not listed  
> at the
> parent servers, which is not correct."

I knew I should have taken a screen shot :)
I consistently get a "No NS A Records at nameservers"

Here is what I see:

For the sake of being thorough, here is mine, same error:

> $ dig soa +short

Well hey, that +shore option is pretty nice, thanks!

> Checking your domain: (did you mean this one or  
> another?). The

No, that one is relevant, though I suspect since this comes back to a  
NS, it is going to say that for all my zones.

> error is a different one.
> Your name servers:
> $ dig ns +short
> Now the report wants to check each name server:
> $ dig +short
> That worked.
> $ dig
> ; <<>> DiG 9.4.2-P2 <<>>
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 24774
> ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
> ;; WARNING: recursion requested but not available
> ;                 IN      A
> This one didnt
> So to answer your question "what is this error asking of me?". It  
> wants
> to reply as did. Specifically to  
> answer an
> A record query for

To make sure I understand, as I am finding the No A record error on  
average 80% of the random domains I am comparing against...

In my zone for I would add in IN A

I am not sure I understand this.  I am not in any way in control of  They merely slave my server.  They obviously have an A  
record for, and can maintain and control that.

I would be adding in an A record, pointing to an IP address, and now  
have to watch and maintain their IP space, to be sure that IP does not  
ever change.  If it does change, and I am not on top of that, things  
are going to get a little wonky.

* Please refer to the screen shots in this email, I am going to toss  
in some test records now, so your results may not match up well if you  
do live testing.
Scott * If you contact me off list replace talklists@ with scott@ *

More information about the bind-users mailing list