Domain Name Lookup
Simple forward and reverse Domain Name System (DNS) lookups.
Monitor Domain Name Lookup automatically
Simple forward and reverse Domain Name System (DNS) lookups. NetTests can run this check on a schedule, preserve historical results, compare changes over time, and alert you the moment something breaks.
Start monitoring free → See all monitoring productsFrequently Asked Questions
What does the Domain Name Lookup show?
The answer to one query — the record or records for the name and type you asked for — without the AUTHORITY and ADDITIONAL sections the DNS Query Tool shows. It is the quickest way to check what a name resolves to, and it accepts an IP address for a reverse (PTR) lookup.
Why might my own computer get a different answer?
This lookup is made from our server, through its resolver. Your computer asks its own resolver — your router, ISP or company network — which may have cached an older answer, or be served a different one by geo-aware DNS. If the two disagree, the difference is usually a cache that has not expired yet.
What DNS record types should I know?
- A — IPv4 address of the domain.
- AAAA — IPv6 address.
- CNAME — alias pointing to another hostname.
- MX — mail server(s) for the domain.
- TXT — free-text records; used for SPF, DKIM, domain verification.
- NS — nameservers authoritative for the domain.
- SOA — start-of-authority; holds the primary NS and serial number.
- PTR — reverse DNS; maps an IP to a hostname.
What is TTL and why does it matter?
Time To Live (TTL) is the number of seconds resolvers are allowed to cache a Domain Name System (DNS) record. A TTL of 300 means the record may be cached for up to 5 minutes. Lower TTLs allow faster propagation of changes; higher TTLs reduce DNS query load but mean old records stick around longer after a change.
Why do I get different results from different resolvers?
Results can differ due to caching (each resolver may have cached a different version), geo-DNS (some Content Delivery Networks (CDNs) return different IPs based on the resolver's location), or propagation delays after a recent Domain Name System (DNS) change. Use the DNS Propagation tool to query many resolvers simultaneously.