7062 error - help me completely understand causes.

[Bob Z]

I've read Microsoft's article explaining the 4 causes of a
DNS server sending a packet to itself:

1. DNS forwarders - should not send to itself. OK, that's
obvious. I checked the server and I'm okay there.

2. Master lists of secondary zones - What does this mean?
Where am I supposed to look??

3. Notify lists of primary zones - Again, what is this
referring to? Where do I look to see if this is the
problem?

4. Delegations of subzones - comes with an explanation. I
sort of understand but it could be clearer. We do have 1
sub-zone in our DNS.

-muchas gracias,
el bob

 

[Kevin D. Goodknecht [MVP]]

In

I've read Microsoft's article explaining the 4 causes of a
DNS server sending a packet to itself:

1. DNS forwarders - should not send to itself. OK, that's
obvious. I checked the server and I'm okay there.

There was a poster here a couple of weeks ago that had put his own server in
the Root Hints that caused this. I'm not saying that is what you did, I'm
just reporting what his cause was.

2. Master lists of secondary zones - What does this mean?
Where am I supposed to look??

On the zone transfer tab, if you have selected "Allow zone transfers to the
server on the Nameserver tab" it will try to send a zone transfer to itself.

3. Notify lists of primary zones - Again, what is this
referring to? Where do I look to see if this is the
problem?

On the Zone transfer tab, "Notify" button, if you have select "Notify
servers on the Name Server Tab" it will notify itself of a zone transfer.

4. Delegations of subzones - comes with an explanation. I
sort of understand but it could be clearer. We do have 1
sub-zone in our DNS.

Do you have a delegated subzone in your DNS? If it does:
Does the delegation have an NS record of itself? If it does:
Do you have a separate Forward Lookup zone on the server for
"subzone.domain.com"? If it does NOT, that is the cause.