DNS Lookup

DNS is the internet’s phone book. When you type a website name, your device asks a resolver for records that point to IP addresses, mail servers, or verification strings. A DNS lookup tool lets you inspect those records directly so you can verify a domain migration, debug email delivery, confirm a CDN change, or see whether a hostname still points at an old VPS. Home users also use lookups after changing router DNS settings to public resolvers, to confirm that queries still resolve cleanly.

Routerpedia’s free DNS Lookup queries common record types through DNS-over-HTTPS, which is convenient on networks that interfere with classic DNS ports. It complements our router-focused guides: after you set custom DNS on a gateway, you can validate public records for your domain or for services you rely on daily.

A records map a name to an IPv4 address. AAAA records do the same for IPv6. If a site loads for some people and not others, comparing A/AAAA answers can reveal partial dual-stack problems. CNAME records alias one name to another and are common for www or CDN hostnames. MX records tell the world which servers accept email for the domain; priority numbers decide preference order. NS records list authoritative nameservers. TXT records hold SPF, DKIM, DMARC, domain verification tokens, and other metadata. SOA describes zone authority and timing parameters used by secondary nameservers.

You do not need every type for casual browsing, but if you run a personal site, small business mail, or a self-hosted service behind a home connection (with dynamic DNS), understanding these records prevents guesswork. When port-forwarding a server, your A record must point at your current public IP unless you use a tunnel.

Most routers advertise DNS servers to LAN clients through DHCP. By default that is often your ISP’s resolvers. Many people switch to Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9, or a filtering DNS for malware blocking. After changing WAN or LAN DNS fields, reboot clients or renew DHCP leases so devices pick up the new servers. If browsing fails entirely, revert to automatic DNS and test again — a typo in a custom DNS IP can break name resolution while ping to numeric IPs still works.

Some ISPs use special private DNS for TV or voice services; overriding DNS on the router can affect those features. Guest networks may inherit or override parent DNS. If parental controls live in DNS filtering, document which resolver you chose so future firmware resets are easy to restore. Our ISP lookup helps you identify the provider when support asks which network you are on.

When you update DNS at your registrar, resolvers around the world may cache the previous answer until the TTL expires. That is why one lookup tool can disagree with another for a few minutes or hours. Flushing local caches (browser, OS, or router) can help your own devices, but you cannot force every recursive resolver on the internet to refresh immediately. Plan migrations with lower TTLs ahead of time when possible.

Negative caching also exists: if a name truly does not exist, resolvers may remember the failure briefly. Typos in the domain field of this form are a common “no records” cause — always verify spelling. For mail issues, check MX and related TXT records together; fixing only the website A record will not repair SPF failures.

Home labs sometimes run local DNS forwarders — Pi-hole, AdGuard Home, or router firmware with custom entries — that answer certain names differently from the public internet. A hostname might resolve to a private IP inside the house while the world sees a CDN address. This lookup tool queries Cloudflare’s public resolver, so it shows the global view. If your laptop gets one answer and this tool another, you likely have split-horizon DNS working as designed.

Router “DNS override” or “local domain” fields let you map nas.home to a LAN server without buying a public domain. Document those overrides before firmware resets. When migrating off an old Pi-hole, compare NS and A records here against your registrar so email and VPN names still resolve. Subnet planning for DNS servers themselves belongs in the Subnet Calculator if you dedicate a fixed LAN IP to the resolver.

Mail deliverability depends on MX, SPF (TXT), DKIM (TXT), and sometimes DMARC (TXT) all aligning. A common failure mode is pointing the website A record to a home public IP while MX still references an old host. Lookup each record type separately in this form. TXT strings may wrap or split; read the full data column. After ISP IP changes, update dynamic DNS A records before wondering why remote webmail stopped syncing.

Self-hosted Nextcloud, game servers, and cameras behind port forwarding need stable names. Verify A/AAAA answers after every WAN IP change. If only IPv6 clients reach you, ensure AAAA exists and firewall rules match. Combine DNS checks with proxy detection when geoblocked CDNs serve different answers by region — not every “DNS problem” originates on your router.

Retail routers usually offer “automatic DNS from ISP” or manual fields for primary and secondary servers. Public resolvers like 1.1.1.1, 8.8.8.8, and 9.9.9.9 add logging policies, malware blocking tiers, and DoH/DoT support on some models. Family filters trade privacy for category blocking — understand the vendor’s data handling before enabling. After changes, renew DHCP on a test laptop and run a lookup here to confirm general resolution still works.

Some mesh systems hide DNS behind an app toggle labeled “security” or “family.” Document what you enabled; blind resets cause mysterious blocks of legitimate shops or banking sites. ISP-provided DNS may be required for IPTV VLANs — if TV stops working after custom DNS, revert WAN settings and test again. Identify your provider with What is my ISP? when calling support about resolver-specific outages.

Google Public DNS uses 8.8.8.8 as the primary resolver and 8.8.4.4 as the secondary. People search for “8.8 8.8 ip” or “dns 8.8” when they want a reliable alternative to ISP resolvers. Enter these values in your router’s DNS fields (or on a single PC), not as a website login. They do not open an admin panel the way 192.168.1.1 does.

Cloudflare DNS uses 1.1.1.1 (primary) and 1.0.0.1 (secondary). Searches for “1.1 1.1 ip address” almost always mean this public resolver. Some phones also offer a 1.1.1.1 app for DNS over HTTPS/TLS; router-level settings still help every device on Wi‑Fi at once.

After you switch, open this DNS Lookup tool and query a site you know well (for example your email domain’s MX/TXT records, or a simple A record). If names fail to resolve, double-check you did not swap digits (8.8.8.8 vs 8.8.4.4) and that you saved WAN vs LAN DNS fields correctly. Pair with What is my IP? only when testing remote access — DNS and public IP solve different problems.

Quick router checklist: (1) log into your gateway admin page, (2) find Internet / WAN / DHCP DNS settings, (3) set primary/secondary to 8.8.8.8 + 8.8.4.4 or 1.1.1.1 + 1.0.0.1, (4) save and reboot or renew leases, (5) verify with this lookup. If you need step-by-step admin access first, read How to log into your router.

DNS lookups for public domains are a normal administrative action. This tool sends queries to a public DoH resolver from your browser; do not paste secrets into the domain field. We do not need your router password to look up public records. If you are investigating phishing, remember that DNS alone does not prove a site is safe — combine with caution and official vendor domains.

Continue with Subnet Calculator for LAN planning, or browse all utilities on the free network tools page. Routerpedia exists to make router and connection troubleshooting clearer for homeowners and small offices — without requiring paid desktop software.