Re: DNS warning.

To update root hints on the DNS server
Open DNS.

In the console tree, click the applicable DNS server.


• DNS/applicable DNS server

On the Action menu, click Properties.

Click the Root Hints tab.

Modify server root hints as follows:

• To add a root server to the list, click Add, and then specify the name and
IP address of the server to be added to the list.

• To modify a root server in the list, click Edit, and then specify the name
and IP address of the server to be modified in the list.

• To remove a root server from the list, select it in the list, and then
click Remove.
If you see the name of your server here REMOVE IT.

• To copy root hints from a DNS server, click Copy from server, and then
specify the IP address of the DNS server from which you want to copy a list
of root servers to use in resolving queries. These root hints will not
overwrite any existing root hints.

If you do not have another server to copy the files from do the following.
Remove your server from the root hints.
close the DNS Tab
go to start Run
type the following: C:\Windows\system32\DNS
hit enter
you will see the Cache.DNS File
Open it with word pad. make sure to uncheck the always open this type of
file with this program check mark.
copy these DNS servers and paste them into the file. This is the stardard
DNS configuration with all known servers that point to .com, net, .org etc.

@ NS A
@ NS A
@ NS A
@ NS A
@ NS A
@ NS A
@ NS A
@ NS A
@ NS A
@ NS A
@ NS A
@ NS A
@ NS A


• To perform this procedure, you must be a member of the Administrators
group on the local computer, or you must have been delegated the appropriate
authority. If the computer is joined to a domain, members of the Domain
Admins group might be able to perform this procedure. As a security best
practice, consider using Run as to perform this procedure.

• To open DNS, click Start, click Control Panel, double-click Administrative
Tools, and then double-click DNS

After you do this Run the IPconfig/Flush DNS command
Then run the Ipconfig/registerdns
Reboot the server and your problem should be gone.

"beeboo_beeboo@xxxxxxxxxxx" wrote:

how can i do this... please help

"Rayden" <Rayden@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
This problem i seen it happening when you first install active directory
using the wizard to automatically configure DNS. because the server does
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)
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
The DNS server encountered a packet addressed to itself on IP address The packet is for the DNS name
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 is the primary for the
-> The zone contains a delegation of to,
( NS
-> BUT the zone is NOT on this server.

Note, you should make this delegation check (with nslookup or DNS
both on this DNS server and on the server(s) you delegated the subzone
It is possible that the delegation was done correctly, but that the
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
this problem.

For more information, see Help and Support Center at
0000: 50 25 00 00 P%..


Relevant Pages