Network & Certificates

DNS & domain tools

DNS troubleshooting covers a wide range: checking why an MX or TXT record isn't propagating, editing a BIND zone file by hand, validating a hostname before it goes into a config file, or working out the PTR name for a reverse DNS zone. This page groups live DNS queries together with offline tools for zone files, validation and domain name encoding.

The DNS lookup tool queries A, AAAA, MX, TXT, CNAME, NS, SOA, CAA and PTR records against real name servers, so it's the one tool here that contacts a network service; the zone editor, domain validator, reverse DNS generator and punycode converter all work on text you provide, entirely in the browser. Reach for the punycode converter specifically when a domain contains non-ASCII characters and you need the ASCII form DNS actually stores.

5 tools

DNS & Domains tools FAQ

Why does a domain with accented characters look different in a browser bar than in DNS?

DNS only stores ASCII, so internationalized domain names are transformed into an ASCII-compatible Punycode form starting with xn-- before they're looked up. The punycode converter shows both the Unicode and Punycode form of a domain side by side so you can confirm they match.

How do I build a PTR record for reverse DNS?

A PTR name is derived from the IP address written in reverse, under in-addr.arpa for IPv4 or ip6.arpa for IPv6. The reverse DNS name generator builds that name for you from an IPv4 or IPv6 address, including the aligned CIDR zone name for delegated blocks.

Why would I edit a zone file by hand instead of using a DNS provider's UI?

A BIND zone file is the portable, provider-independent format for a domain's records, useful when migrating providers or reviewing a diff in version control. The DNS zone editor parses that file format directly and lets you build records with the correct TTL and context.