How to remove the Domain Controllers (DCs) demoted still showing in DNS

Even the DCs demoted.

But continued at DNS.

To remove them.

Run:
dnsmgmt.msc


Modify the Name Servers:
1. Forward Lookup Zones

Note: X = _msdcs.domain.org / domain.org


2. Check & remove the DCs demoted:
_kerberos._tcp.X Enables a client to locate a server that is running the Kerberos KDC service for the domain that is named in DnsDomainName. The server is not necessarily a domain controller.
_ldap._tcp.X Enables a client to locate a server that is running the LDAP service in the domain named DnsDomainName. The server is not necessarily a domain controller — that is, the only assumption that can be made about the server is that it supports the LDAP application programming interface (API). All Windows Server 2003–based domain controllers register this SRV record (for example, _ldap._tcp.contoso.com.).
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.X Enables a client to locate a server that is running the Kerberos KDC service for the domain that is named DnsDomainName and is also in the site named SiteName. The server is not necessarily a domain controller. All Windows Server 2003 and later based domain controllers that are running an RFC 1510–compliant Kerberos KDC service register this SRV record.
_kerberos._tcp.dc._msdcs.X Enables a client to locate a domain controller that is running the Windows Server 2003 or later implementation of the Kerberos KDC service for the domain named in DnsDomainName. All Windows Server 2003 and later based domain controllers that are running the KDC service (that is, that implement a public key extension to the Kerberos v5 protocol Authentication Service Exchange subprotocol) register this SRV record.
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.X Enables a client to locate a domain controller for the domain named DnsDomainName and in the site named SiteName. All Windows Server 2003 and later based domain controllers register this SRV record.
_ldap._tcp.dc._msdcs.X Enables a client to locate a domain controller (dc) of the domain named DnsDomainName. All Windows Server 2003 and later based domain controllers register this SRV record.
_ldap._tcp.DomainGuid.domains._msdcs.X Enables a client to locate a domain controller in a domain on the basis of its GUID. A GUID is a 128-bit number that is automatically generated for referencing objects in Active Directory — in this case, the domain object. This operation is expected to be infrequent; it occurs only when the DnsDomainName of the domain has changed, the DnsForestName is known, and DnsForestName has not also been renamed (for example, _ldap._tcp.4f904480-7c78-11cf-b057-00aa006b4f8f.domains. _msdcs.contoso.com.).

All domain controllers register this SRV record.
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.X Enables a client to locate a global catalog (gc) server for this forest in the site named in SiteName. Only domain controllers that are serving as gc servers for the forest named in DnsForestName register this SRV record (for example, _ldap._tcp.charlotte._sites.gc._msdcs.contoso.com.).
_ldap._tcp.gc._msdcs.X Enables a client to locate a global catalog (gc) server for this forest. Only domain controllers that are functioning as gc servers for the forest named in DnsForestName register this SRV record (for example, _ldap._tcp.gc._msdcs.contoso.com.).

 
References


Update