How do I check a server’s DNS records from Windows?
Query the specific record type for the server name and compare it with the current assigned address. DNS records describe name resolution; they do not prove that the service at the returned address is running.
Instructions
1. Query IPv4 and IPv6 records in PowerShell
Use the actual fully qualified server name.
Resolve-DnsName -Name vps.example.com -Type A -DnsOnly
Resolve-DnsName -Name vps.example.com -Type AAAA -DnsOnlyA records describe IPv4 addresses and AAAA records describe IPv6 addresses. A server need not publish both.
2. Use the CMD alternative
nslookup is useful where the PowerShell DNS module is unavailable.
nslookup -type=A vps.example.comReview both the answering resolver and returned records. This command queries DNS rather than proving how every application resolves the name.
3. Check propagation and scope deliberately
Compare with the authoritative DNS configuration and expected TTL. A private hostname may resolve only through a VPN or internal resolver. Do not replace a working resolver globally just because one record looks stale.
Check the result
- The returned address matches the intended current server endpoint.
- The actual service works at the resolved address with normal identity verification.
Troubleshooting
- No AAAA record exists
- That can be intentional for an IPv4-only service; it is not automatically a fault.
- Different networks return different answers
- Investigate caching, split DNS, resolver policy and intentional traffic distribution before changing records.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.