DNS in 2003 server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi everybody,

I always get the following two warnings from DNS. Can anyone inform me about
the reasons and solutions?

1) The DNS server has encountered numerous run-time events. To determine the
initial cause of these run-time events, examine the DNS server event log
entries that precede this event. To prevent the DNS server from filling the
event log too quickly, subsequent events with Event IDs higher than 3000 will
be suppressed until events are no longer being generated at a high rate.

2) The DNS server encountered a packet addressed to itself on IP address
82.222.180.174. The packet is for the DNS name "ns.wineasy.se.". The packet
will be discarded. This condition 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.
5) Root hints.

This one appears for many different domains.

Thanks
 
In
Ceyhun said:
Hi everybody,

I always get the following two warnings from DNS. Can
anyone inform me about the reasons and solutions?
Click to expand...

The reason for the warning is listed in the data of the event you listed as
2). See below.
1) The DNS server has encountered numerous run-time
events. To determine the initial cause of these run-time
events, examine the DNS server event log entries that
precede this event. To prevent the DNS server from
filling the event log too quickly, subsequent events with
Event IDs higher than 3000 will be suppressed until
events are no longer being generated at a high rate.

2) The DNS server encountered a packet addressed to
itself on IP address
82.222.180.174. The packet is for the DNS name
"ns.wineasy.se.". The packet will be discarded. This
condition usually indicates a configuration error.

Check the following areas for possible self-send
configuration errors:
Click to expand...

1) Forwarders list. (DNS servers should not forward to themselves).

This one is self explanitory.

2) Master lists of secondary zones.

If the server has a secondary zone on it, it should not have its own address
listed a master server on the general tab.

3) Notify lists of primary zones.

If the server has a zone on it configured to allow zone transfers and to
notify it secondary servers to do a zone transfer, it should not have its
own address be notified. This is common if you have "Notify the DNS servers
listed on the Name Server tab" and it has its own NS record listed on the
name server tab.
This notify option is for hidden masters. A hidden master DNS that doesn't
have an NS record and is not listed as Authortative on the public record,
but is where the secondary servers that are listed on the public record get
their zone data from.

4) Delegations of subzones. Must not contain NS record for this DNS server
unless subzone is also on this server.

Just as this one says, if a zone as a delegated subzone and it has its own
NS record in the delegation, it must have a subzone in its list of zones.
e.g. if you have a zone, 'example.com' and 'example.com' has a delegation
named 'sub', there must also be a zone named 'sub.example.com'

5) Root hints.

Check your Root Hints tab to make sure it does not have its own name and
address listed there.
 
Back
Top