DNS server polling itself?

  • Thread starter Thread starter eotrue
  • Start date Start date
E

eotrue

We have 2 Win2K (SP4) domain servers which are also dns
servers. There are working fine. I am getting this error
message from one of them and not the other. I have
compared the 2 and I cannot find a difference in the
configuration.

I have also investigated the suggestions that accompany
the error message and we do not have any of the problems
that they say to look for.

There are no subzones. They do forward requests to public
servers. We are receiving this message about 2 times
every 15 minutes.

Regard,

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 3/19/2004
Time: 10:04:18 AM
User: N/A
Computer: SERVER_NAME
Description:
The DNS server encountered a packet addressed to itself --
IP address 192.168.2.3.

The DNS server should never be sending a packet to
itself. This situation usually indicates a configuration
error.

Check the following areas for possible self-send
configuration errors:
1) Forwarders list. (DNS servers should not forward to
themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record
for this DNS server unless subzone is also on this server.
 
In
eotrue said:
We have 2 Win2K (SP4) domain servers which are also dns
servers. There are working fine. I am getting this error
message from one of them and not the other. I have
compared the 2 and I cannot find a difference in the
configuration.

I have also investigated the suggestions that accompany
the error message and we do not have any of the problems
that they say to look for.

There are no subzones. They do forward requests to public
servers. We are receiving this message about 2 times
every 15 minutes.

Regard,

Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 3/19/2004
Time: 10:04:18 AM
User: N/A
Computer: SERVER_NAME
Description:
The DNS server encountered a packet addressed to itself --
IP address 192.168.2.3.

The DNS server should never be sending a packet to
itself. This situation usually indicates a configuration
error.

Check the following areas for possible self-send
configuration errors:
1) Forwarders list. (DNS servers should not forward to
themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record
for this DNS server unless subzone is also on this server.
Click to expand...


Is this machine mutlihomed?
Are there any delegations?
Are there any subzones?

If you have two DC/DNS servers, suggest to config DNS settings this way:

DC1
DC2
DC1

DC2
DC1
DC2



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
eotrue said:
We have 2 Win2K (SP4) domain servers which are also dns
servers. There are working fine. I am getting this error
message from one of them and not the other. I have
compared the 2 and I cannot find a difference in the
configuration.

I have also investigated the suggestions that accompany
the error message and we do not have any of the problems
that they say to look for.

There are no subzones. They do forward requests to public
servers. We are receiving this message about 2 times
every 15 minutes.
Click to expand...
1) Forwarders list. (DNS servers should not forward to
themselves).
Click to expand...
You stated that this DNS forwards to your ISP and not to itself, if that is
true then this is not the problem
2) Master lists of secondary zones.
Click to expand...
Make sure this DNS server is not sending a zone transfer to itself. It could
be trying to do a zone transfer to itself if you have select "Only to the
name servers listed on the nameserver tab"
3) Notify lists of primary zones.
Click to expand...
On the zone transfer tab click the notify button, make sure this server is
not notifying itself of a zone transfer. Tricky part is that if this server
has an NS record and is listed as a name server, do NOT select "Notify name
servers listed on the nameserver tab"
4) Delegations of subzones. Must not contain NS record
for this DNS server unless subzone is also on this server.
Click to expand...
If you have a delegation and this DNS server has an NS record in the
delegation, it will need a zone for the delegated name. Example if this
server has a zone for domain.com and a delegation in this zone named "child"
then this DNS server will also need a separate zone for "child.domain.com"
 
Back
Top