Overview#
Configure and verify A, PTR, CNAME, and Active Directory SRV records for company.local. Then join a Windows 11 client, sign in with AD accounts, and confirm client A and PTR registration.
Lab Environment#
| Component | Value |
|---|---|
| Windows Server | Windows Server 2025 Standard, 24H2, build 26100.32690 |
| Domain / DNS server | company.local / company-ad.company.local (198.18.134.50) |
| ISE host | ise121.company.local (198.18.134.121) |
| Subnet / gateway | 198.18.128.0/18 (255.255.192.0) / 198.18.128.1 |
| Windows 11 client | WINDOWS-UCEQTFN, 198.18.134.60 |
| Client DNS servers shown | 198.18.134.50 and 8.8.8.8 |
| Windows 11 client version | Windows 11 25H2 |
Prerequisites#
- Existing AD DS and DNS for company.local.
- DNS administration access and a Windows 11 edition that supports joining an AD DS domain.
- Local administrative access to the client and an AD account allowed to join computers to the domain.
- An enabled AD user for the sign-in test.
Configure and Verify DNS Records#
A record
In the company.local forward lookup zone, create the host record ise121 with address 198.18.134.121.

Figure 1. The ise121 host record values.

Figure 2. The A record appears in company.local.
Verify name resolution and reachability:
1ping ise121.company.localThe hostname resolved to 198.18.134.121; the captured ping received 4 replies with 0% packet loss.

Figure 3. Ping resolves the FQDN and receives four replies.
Reverse lookup zone and PTR records
The IPv4 reverse lookup zone was created with these settings:
- Primary zone, stored in Active Directory.
- Replication: DNS servers on domain controllers in company.local.
- Network ID: 198.18.134.
- Resulting zone: 134.18.198.in-addr.arpa.

Figure 4. Replication is scoped to DNS servers in company.local.

Figure 5. The wizard uses Network ID 198.18.134.

Figure 6. The resulting reverse lookup zone.
Create PTR records for the existing hosts:
| Address | PTR target |
|---|---|
| 198.18.134.50 | company-ad.company.local |
| 198.18.134.121 | ise121.company.local |

Figure 7. DNS Manager shows the two PTR records.
The first reverse queries returned “Non-existent domain.” After adding the PTR records, the captured results resolved both addresses:
| Query | Result |
|---|---|
| company-ad.company.local | 198.18.134.50 |
| 198.18.134.50 | company-ad.company.local |
| ise121.company.local | 198.18.134.121 |
| 198.18.134.121 | ise121.company.local |
CNAME record
Create the alias ise in company.local, targeting ise121.company.local.

Figure 8. The ise alias points to ise121.company.local.
1nslookup -type=CNAME ise.company.local 198.18.134.50
2nslookup ise.company.local 198.18.134.50The captured response identifies ise121.company.local as the canonical name and resolves it to 198.18.134.121.
Active Directory SRV records
Query the LDAP and Kerberos domain-controller locator records:
1nslookup -type=SRV _ldap._tcp.dc._msdcs.company.local 198.18.134.50
2nslookup -type=SRV _kerberos._tcp.dc._msdcs.company.local 198.18.134.50| Service | Port | Target |
|---|---|---|
| LDAP | 389 | company-ad.company.local (198.18.134.50) |
| Kerberos | 88 | company-ad.company.local (198.18.134.50) |
Join the Windows 11 Client and Sign In#
The client used static address 198.18.134.60/18 with gateway 198.18.128.1. The captured DNS list was 198.18.134.50 and 8.8.8.8.

Figure 9. Client IPv4 settings before domain join.
In System Properties > Computer Name > Change, select Domain and enter company.local. Use an account permitted to join the computer, accept the welcome message, and restart.

Figure 10. The client is set to join company.local.

Figure 11. Windows confirms the domain join.

Figure 12. Restart is required to apply the change.
After restart, the first recorded sign-in was with the domain Administrator. The captured whoami result was company\administrator.

Figure 13. whoami confirms the signed-in account belongs to company.
A standard AD user named win11-test was created under company.local/Users. Its UPN is win11-test@company.local.

Figure 14. The win11-test account and UPN.
Sign in as COMPANY\win11-test and verify:
1C:\Users\win11-test>whoami
2company\win11-test
3
4C:\Users\win11-test>whoami /upn
5win11-test@company.local
6
7C:\Users\win11-test>echo %LOGONSERVER%
8\\COMPANY-AD
Figure 15. The standard AD user signs in successfully.
From the Windows 11 client, query the LDAP domain-controller locator record:
1C:\Users\win11-user>nslookup -type=SRV _ldap._tcp.dc._msdcs.company.local 198.18.134.50
2Server: COMPANY-AD.company.local
3Address: 198.18.134.50
4
5_ldap._tcp.dc._msdcs.company.local SRV service location:
6 priority = 0
7 weight = 100
8 port = 389
9 svr hostname = company-ad.company.local
10company-ad.company.local internet address = 198.18.134.50Verify Client DNS Registration#
After the client joined the domain, DNS Manager showed timestamped records for WINDOWS-UCEQTFN:
| Record | Result |
|---|---|
| A | WINDOWS-UCEQTFN.company.local → 198.18.134.60 |
| PTR | 198.18.134.60 → WINDOWS-UCEQTFN.company.local |

Figure 16. The client A record appears in company.local.

Figure 17. The A record properties show 198.18.134.60 and the associated PTR option.

Figure 18. The reverse zone contains the client PTR record.

Figure 19. The PTR target is WINDOWS-UCEQTFN.company.local.
The timestamped A and PTR records show that the client registered its DNS records after joining the domain.
Conclusion#
The A, PTR, CNAME, and LDAP/Kerberos SRV records resolved as captured. The Windows 11 25H2 client joined company.local, the win11-test AD account signed in successfully, and DNS Manager showed the client A and PTR records.