What Is DNS Lookup?

Why It Matters

Every time someone visits your domain, a DNS lookup happens first. The browser needs to find the IP address of the server to connect to. For forwarded domains, this means finding Domain Forward’s server — then the redirect happens.

DNS lookup speed directly affects how fast visitors experience the redirect.

How It Works

1. Browser checks its local DNS cache: “Do I already know the IP for example.com?”
2. If not cached, asks the operating system’s resolver
3. Resolver checks its cache, then queries root → TLD → authoritative nameserver
4. Authoritative nameserver responds with the A record IP address
5. Browser connects to that IP address

You can also perform a reverse DNS lookup — starting with an IP address and finding the associated domain name. Modern privacy-focused resolvers use DNS-over-HTTPS to encrypt these queries.

Browser → "What's the IP for example.com?"
        ← "93.184.216.34" (from A record)
Browser → Connects to 93.184.216.34
        ← 301 Redirect to new-domain.com

DNS Lookup and Redirect Speed

Phase	Typical Time
DNS lookup (cached)	1-5ms
DNS lookup (uncached)	20-100ms
TCP connection	10-50ms
TLS handshake (HTTPS)	10-30ms
Redirect response	<5ms (Domain Forward)
Total	~40-190ms

The DNS lookup is often the slowest part. A good TTL setting ensures repeat visitors skip the full lookup.

How Domain Forward Handles This

Domain Forward uses globally distributed servers to minimize the connection and redirect time. Once DNS points to our servers, the redirect response itself takes under 5ms. We recommend a TTL of 300-3600 seconds for forwarded domains — this balances fast propagation with efficient caching.