RE: DNS warning.



This problem i seen it happening when you first install active directory
using the wizard to automatically configure DNS. because the server does not
find any suitable DNS servers during installation it assigns itself as the
root hints.
I had two servers on my domain so i just copied the root hints from a good
working server to this one. If you go to DNS (administrator tools- DNS) right
click on the DNS server and go to the root hints tab. if you only see your
server listed that is the cause of your problem. you need to remove your
server from there and enter the internet root hints there

hope this helps.

"beeboo beeboo" wrote:

Does any bosy can help me to solve belows warning.... it kept show in the
event log... thanks


Event Type: Warning
Event Source: DNS
Event Category: None
Event ID: 7062
Date: 9/5/2021
Time: 10:08:47 PM
User: N/A
Computer: GRANDSBS2K3
Description:
The DNS server encountered a packet addressed to itself on IP address
192.168.11.254. The packet is for the DNS name "9.131.254.60.in-addr.arpa.".
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.

Example of self-delegation:
-> This DNS server dns1.example.microsoft.com is the primary for the zone
example.microsoft.com.
-> The example.microsoft.com zone contains a delegation of
bar.example.microsoft.com to dns1.example.microsoft.com,
(bar.example.microsoft.com NS dns1.example.microsoft.com)
-> BUT the bar.example.microsoft.com zone is NOT on this server.

Note, 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.

You can use the DNS server debug logging facility to track down the cause of
this problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 50 25 00 00 P%..



.



Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... One thought, when you introduced the Windows Server 2008 and before making them DC's, did you extend the schema on the SBS 2003 server? ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC is unavailable when try to transfer FSMO Roles
    ... on the DNS server ... Registry value: DnsAvoidRegisterRecords ... To stop registration of both NICs, add or alter this ...
    (microsoft.public.windows.server.active_directory)
  • Re: RPC is unavailable when try to transfer FSMO Roles
    ... prevent the public interface addresses from being registered in DNS. ... In the DNS management console, in the properties of the DNS server, ... Registry value: DnsAvoidRegisterRecords ... To stop registration of both NICs, add or alter this reg ...
    (microsoft.public.windows.server.active_directory)