Archived from groups: microsoft.public.win2000.dns (
More info?)
You can only view event logs from a machine with the DNS server installed.
The text of those events is pasted below. You should follow the steps to
search for mis-configurations.
The DNS server encountered a packet addressed to itself -- IP address %1.
%n
%nThe DNS server should never be sending a packet to itself. This situation
usually
indicates a configuration error.
%n
%nCheck the following areas for possible self-send configuration errors:
%n 1) Forwarders list. (DNS servers should not forward to themselves).
%n 2) Master lists of secondary zones.
%n 3) Notify lists of primary zones.
%n 4) Delegations of subzones. Must not contain NS record for this DNS
server
unless subzone is also on this server.
%n
%nExample of self-delegation:
%n -> This DNS server dns1.foo.com is the primary for the zone foo.com.
%n -> The foo.com zone contains a delegation of bar.foo.com to
dns1.foo.com,
%n (bar.foo.com NS dns1.foo.com)
%n -> BUT the bar.foo.com zone is NOT on this server.
%n
%nNote, you should make this delegation check (with nslookup or DNS manager)
both
on this DNS server and on the server(s) you delegated the subzone to.
It is possible that the delegation was done correctly, but that the primary
DNS for the subzone, has any incorrect NS record pointing back at this
server.
If this incorrect NS record is cached at this server, then the self-send
could result. If found, the subzone DNS server admin should remove the
offending NS record.
"Steve Rulison" <anonymous@discussions.microsoft.com> wrote in message
news:226ea01c45de8$3decc720$a601280a@phx.gbl...
> Per your request, I have attached the information
> regarding our DNS servers.
>
> Thank you for your assistance.
>
> Note:
> The two domain controllers currently running DNS are
> identified as FS-DC-1 and DB2SERVER. There are also two
> additional domain controllers that were running on our
> network identified as SP1 and SP2 but they are not
> currently running at this time. They are however still
> listed in the Active Directory DNS listing with identical
> zones.
>
> 1. WHAT OBSERVATIONS ARE YOU BASING THIS ON?
>
> Error messages appearing on a daily basis in the DNS Event
> log
>
> 2. ARE THERE ANY ERRORS ON ANY OF THE DCS' EVENT LOGS -
> LOOKING FOR NTFRS, NETLOGON, KERBEROS, AND LDAP ERRORS?
>
> Yes we have in the past but I did not find any error
> messages in our log at the time of this writing that
> referred to any of the entities mentioned above. I have
> listed below the error message that is continually written
> to the DNS event log.
>
> Error Message on FS-DC-1:
> The description for Event ID ( 7062 ) in Source ( DNS )
> cannot be found. The local computer may not have the
> necessary registry information or message DLL files to
> display messages from a remote computer. You may be able
> to use the /AUXSOURCE= flag to retrieve this description;
> see Help and Support for details. The following
> information is part of the event: 10.44.1.210.
>
> Error Message on DB2SERVER:
> The description for Event ID ( 7062 ) in Source ( DNS )
> cannot be found. The local computer may not have the
> necessary registry information or message DLL files to
> display messages from a remote computer. You may be able
> to use the /AUXSOURCE= flag to retrieve this description;
> see Help and Support for details. The following
> information is part of the event: 10.44.1.18.
>
> 3. PLEASE POST FROM EACH DC AN UNEDITED IPCONFIG/ALL
>
>
>
>
> IPCONFIG For DB2SERVER
>
> Microsoft Windows 2000 [Version 5.00.2195]
> (C) Copyright 1985-2000 Microsoft Corp.
>
> H:\>IPCONFIG /ALL
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : db2server
> Primary DNS Suffix . . . . . . . : ilptab.il.us
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : ilptab.il.us
> il.us
>
> Ethernet adapter Springfield Primary 10.44.1.18:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R)
> PRO/100+ Server Adapter (PI
> LA8470B)
> Physical Address. . . . . . . . . : 00-E0-18-29-B8-
> E1
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 10.44.1.18
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 10.44.1.1
> DNS Servers . . . . . . . . . . . : 10.44.1.18
> 10.44.1.210
>
> IPCONFIG For FS-DC-1
>
>
>
>
>
> >-----Original Message-----
> >I work for a small state agency that only has thirty
> users
> >that can possibly be logged on at any given time. We
> >currently have three domain controllers running on our
> >network and all of them have their own copy of DNS
> >installed. It was my belief at the time I set this
> >network up that this approach would add redundancy to our
> >network and allow for a failure of one of the servers w/o
> >bringing down the entire network. In addition, I also
> >felt that this would provide some load balancing and help
> >keep the network running faster and smoother. I have
> >recently been having some second thoughts on that
> >strategy. It seems that some of the DNS servers are not
> >synchronizing with the other servers on the network.
> Can
> >somebody tell me if I was correct in using this approach
> >or would it have been better off to only have one server
> >running DNS since our agency is so small?
> >.
> >
Facebook
Twitter
Instagram