DNS, DHCP & IP Address Management appliances
For Microsoft DNS & DHCP servers
For open source DNS & DHCP servers
Cloud-based visualization of analytics across DDI architecture
Manage multi-vendor cloud DNS servers centrally
RIR Declaration Management and Automation
Automated network device configuration and management
Centralized visibility over all your clouds
A single source of truth for your network automation
Why DDI is an Obvious Starting Point
DNS Threat Intelligence for proactive defense
Intelligence Insights for Threat Detection and Investigation
Adaptive DNS security for service continuity and data protection
Improve Application Access Control to prevent spread of attacks
Protect users and block DNS-based malware activity
Carrier-grade DNS DDoS attack protection
Optimize application delivery performance from the edge
for Proactive Network Security
Visibility, analytics and micro segmentation for effective Zero Trust strategy
Enable work from anywhere by controlling access, security and data privacy
Simplify management and control costs across AWS, Azure and GCP environments
Policy enforcement, risk management, and automation for simplifying compliance
Risk-free migration to reduce DDI complexity and cost
Move risk-free to improve performance, security and costs
Automate management, unify control and strengthen security of connected devices
Protect your network against all DNS attacks, data exfiltration and ransomware
Enable zero touch operations for network management and security
Improve resiliency, deployment velocity and user experience for SD-WAN projects
Integrated DNS, DHCP, IPAM services to simplify, automate and secure your network.
Simplify design, deployment and management of critical DDI services for telcos
Optimize administration and security of critical DDI services for healthcare
Simplify and automate management of critical DDI services for finance
Simplify and automate management of critical DDI services for higher education
Simplify and automate management of critical DDI services for retail
Simplify Management and Automation for Network Operations Teams
Elevate SecOps Efficiency by Simplifying Threat Response
Enable DevOps practices to deliver consistent network operations.
Open architecture for DDI integration
Technology partnerships for network security & management ecosystems
Extend security perimeters and strengthen network defenses
Submit requests for temporary licenses
Submit access requests for EfficientIP knowledge platforms
Submit membership requests for EfficientIP Community
Strengthen your network security with insights from the Forrester 2025 Study on DNS Security.
Customer-centric DDI project delivery and training
Acquire the skills needed to manage EfficientIP SOLIDserver™
Identify vulnerabilities with an assessment of your DNS traffic
Test your protection against data breaches via DNS
Dedicated representation for your organization inside EfficientIP
Explore content which helps manage and automate your network and cloud operations
Read content which strengthens protection of your network, apps, users and data
Learn how to enhance your app delivery performance to improve resilience and UX
See all your assets in one place
This enterprise-grade cloud platform allows you to improve visibility, enhance operational efficiency, and optimize network performance effortlessly.
Who we are and what we do
Meet the team of leaders guiding our global growth
Technology partnerships for network security and management ecosystems
Make your cloud projects successful with insights from the 2025 EMA Hybrid Multi-cloud Report.
Discover the benefits of the SmartPartner global channel program
Become a part of the innovation
The latest updates, release information, and global events
Active Directory DNS enables clients and servers to locate domain controllers for authentication and replication. Healthy AD depends on accurate SRV records, reliable resolution, secure dynamic updates and consistent DNS data across servers.
November 19, 2026 | Written by: Andreas Taudte | DNS
Summary
Tags
Active DirectoryDDIDNSDNS TroubleshootingDynamic DNSIPAMMicrosoft DNSSRV Records
Active Directory Domain Services (AD DS) stores identities, policies and directory information. DNS publishes the information needed to locate its services. An AD domain and a DNS domain remain distinct concepts even when they share a name.An AD-integrated DNS zone stores records in AD DS and distributes them through directory replication. This creates a dependency in both directions: AD needs DNS to locate replication partners, while these DNS zones depend on healthy AD replication to distribute changes.The fact that multiple DNS servers respond does not necessarily mean that each of these servers possesses up-to-date DNS records. Therefore, availability and data consistency must each be verified separately.
An SRV record maps a service and transport protocol to a target hostname and port, with priority and weight values. For a single-domain forest named ad.example.com, common examples include:
The DC Locator process queries appropriate SRV records, resolves target hostnames to addresses and checks candidate domain controllers using UDP-based LDAP pings. Site information helps it find a suitable nearby controller, and discovered controller information is cached.An SRV answer therefore proves only part of the path. Its target must resolve through valid A or AAAA records, and the advertised services must be reachable. DNS does not continuously verify that a published controller remains healthy.If clients select an unexpected site, check AD subnet-to-site mappings and site-specific records. Adding another domain-wide SRV record does not correct an incorrect site mapping.
Dynamic DNS updates let authorized systems add or remove records without manually editing zone data. Netlogon registers a domain controller’s locator records. Host address and PTR registration involves Windows clients and, depending on configuration, DHCP servers.Document who updates each record type. A DHCP server taking over updates can encounter existing records owned by another account, even when name resolution works normally.For Microsoft AD-integrated zones, use secure dynamic updates. Windows uses Kerberos-based authentication with GSS-TSIG. Record permissions determine whether the authenticated updater can modify a name. Investigate failed authentication or ownership before changing update security. Successful queries do not prove that updates work. Check the Start of Authority (SOA) response used to discover the update destination, confirm registration reaches a writable authoritative server, and verify changes through the resolvers clients use.DNS Scavenging removes eligible stale records according to aging settings. Review refresh behavior, DHCP leases, replication and static-record exceptions before enabling or tightening it. Incorrect scavenging settings can remove legitimate records.A record’s TTL controls caching. It does not remove an obsolete record from its authoritative zone. Lowering TTL cannot repair failed registration or cleanup.
A reverse lookup zone holds PTR records that map IP addresses back to names. IPv4 uses in-addr.arpa. IPv6 uses ip6.arpa.Reverse zones help administrators interpret logs, identify endpoints and investigate inconsistencies between names and addresses. Create and maintain them alongside the forward zones and address ranges they support, with clear responsibility for PTR updates. If DHCP performs DNS updates, investigate missing reverse zones and PTR update failures too.PTR records are optional in DNS, and basic AD domain controller discovery uses forward service and address lookups. Some applications impose additional reverse-resolution requirements, so assess those separately.If a lookup tool reports the DNS server as “Unknown,” inspect the PTR record for that server’s address. That label alone does not establish that forward resolution or AD discovery is broken.
Start on an affected client and compare its results with a working client in the same site.
Inspect ipconfig /all, including VPN adapters, DNS servers and suffixes. Every configured resolver must correctly resolve the internal AD namespace.Avoid adding a public resolver as an alternate for AD clients. A negative answer for an internal name can be accepted without trying another server. Follow Microsoft’s DNS client configuration guidance, and handle external resolution through the internal DNS architecture.
Use illustrative values below, replacing the domain, resolver address and controller name with your environment’s values. Run the address query against the targets returned by the SRV query.Resolve-DnsName _ldap._tcp.dc._msdcs.ad.example.com. -Type SRV -Server 192.0.2.53Resolve-DnsName dc01.ad.example.com. -Type A -Server 192.0.2.53nltest /dsgetdc:ad.example.com /forcenltest /dsgetsiteRepeat queries against each configured resolver; check AAAA records where IPv6 is used. The nltest commands test discovery and report the client’s AD site. Verify connectivity to the returned controller’s required services.
On a domain controller or management host with the appropriate AD tools and permissions, start with dcdiag /test:dns /DnsBasic /v /s:dc01.ad.example.com and inspect repadmin /replsummary. Replace the example controller name with your target. Use Microsoft’s DNS diagnostic guidance to select further tests.Compare published locator records with %SystemRoot%\System32\Config\Netlogon.dns. Protect the _msdcs namespace, including GUID-based CNAME records used to find replication partners. Event ID 2087 identifies a DNS lookup failure that prevented replication with a source controller.Record the failing query, responding server, answer and timestamp before flushing caches. A cache flush may expose a corrected answer, but it cannot fix authoritative data.
AD and network teams need a shared view of zones, forwarding, update ownership and changes. The inventory approach in DNS architecture foundations provides a practical starting point.EfficientIP’s IPAM for Microsoft centralizes management and visibility across Microsoft DNS, DHCP and IP address data. Overlay management offers a way to bring existing services into a common operational view.Include client-side SRV queries, target resolution, update verification and replication checks in routine health reviews, especially after controller promotions, demotions, subnet changes or DNS migrations.
Healthy AD requires accurate service advertisements, reliable DNS paths, reachable controllers and records that stay current. Test that complete dependency during routine operations and infrastructure changes. Start with the affected client’s discovery path, then follow the evidence through registration, zone data and replication.
No, Active Directory can use a compatible non-Microsoft DNS implementation. It needs the required service and address records, reliable resolution and a dependable registration process. Dynamic updates greatly simplify ongoing maintenance. Validate secure-update interoperability and operational requirements when choosing an architecture.
Reverse lookup zones are not a prerequisite for basic AD domain controller discovery. They improve troubleshooting and endpoint identification, and some applications require reverse lookups. Maintain PTR records as part of DNS hygiene while testing forward service discovery separately.
Resolving a controller’s hostname proves that its address record is available through that DNS path. Discovery also depends on appropriate SRV records, site information and connectivity to the advertised services. Test those dependencies from the affected client to locate the failing stage.
Bring Microsoft DNS, DHCP and IP address data into one management view with EfficientIP IPAM for Microsoft to improve visibility, consistency and everyday operations.
Talk to an expert
Summarize
Networks
Explore content highlighting the value EfficientIP solutions bring to your network