Shulou(Shulou.com)06/01 Report--

This article will explain in detail how to find missing DNS records in windows, Xiaobian thinks it is quite practical, so share it with you for a reference, I hope you can gain something after reading this article.

One of the disadvantages of the multi-host replication model of Windows Active Directory applications is that changes replicate quickly, and small errors can turn into large errors in a short time.

Domain Name System (DNS) zones and records may be corrupted, containing incorrect information or even missing.

Found deleted DNS records

DNS records can be deleted manually, some operations can cause this result, such as DC demotions or other object cleanups, and of course DNS records can be deleted programmatically. Remember that this record, like all AD objects, can be deleted on any DC/DNS server, and this replicates to all DCs. One way to keep track is to find deleted objects and look at metadata. The built-in LDP.exe tools on all DC are helpful for this operation.

Also, find DNS records on AD based on replication scope. These locations are as follows. Table 1 shows the LDP tool that displays DNS records. Remember that DNS records only show one of these three locations.

Table 1: Replication Range Locations in AD

When objects are deleted, they are placed in the Deleted Objects folder, as shown in Figure 1. But the deleted DNS object is stored in a repository where other DNS records are stored. For example, in Figure 2, we see DNS records stored in the DC=DomainDNSZones library, but it also has a Delete Objects library.

Figure 1: Deleting Objects

Figure 2: List of DNS records

Remember: To display the Deleted Objects folder (hidden by default in LDP.exe), do the following:

In the LDP.exe tool, connect to a DC and bind the administrator certificate

Go to Options-Control and select "Restore Deleted Objects" in the "Predefined Loads" section.

Refresh by selecting Tree-(Domain Name)-Done

Expand the DC=deletedObjects, dc=domainDNSzones…library and the deleted DNS objects are displayed (Figure 3). In this case, the record we are interested in is "DC=_dcdiag_test_record…" In this case, it's been reconstructed many times. Note that in Figure 3, the attributes shown in LDP(right panel) are not helpful.

The command is in the following format:

Reapadmin /showobjmeta DCName ObjectDN

So in this example, we get the ObjectDN from the LDP tool and insert it like this:

C:\Users\olseng>repadmin /showobjmeta wtec-dc4 "dc=_dcdiag_test_record\0ADEL:ba38f888-9314-4ddf-852d-736db6ae181e,cn=deleted

objects,dc=domaindnszones,dc=wtec,dc=adapps,dc=hp,dc=com" >dnsdelete.txt

Figure 3: Deleted DNS objects

I want it to go straight to a file to make it easier to use. The output is shown in Figure 4. Note that the areas circled in red are attributes. This attribute is established when an object is deleted. Also displayed are the GUID and time stamp of the initial DC. GUID can be resolved to DC name by viewing or running it in CNAME record on DNS snap-in. DC names usually do not appear as GUID. It is now obvious when the record was deleted and on which DC it was executed. This helps solve the mystery of the disappearance of records.

Figure 4: Output of deleted DNS records

About "how to find missing DNS records in windows" this article is shared here, I hope the above content can be of some help to everyone, so that you can learn more knowledge, if you think the article is good, please share it to let more people see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.