Forward and Reverse DNS Lookup Explained (With Examples)
1. Forward Lookup (Name → IP)
Definition
Forward Lookup resolves a domain name (e.g., google.com) to an IP address (e.g., 142.250.190.46).
Purpose
- Enables browsers, apps, and services to locate servers using human-readable names.
- Essential for web browsing, email delivery (MX records), and CDN routing.
Key Components
A (Address) Record
example.com. A 93.184.216.34
AAAA Record (IPv6)
example.com. AAAA 2606:2800:220:1:248:1893:25c8:1946
How DNS Resolver Works in Forward Lookup
- You type example.com in the browser → OS checks local DNS cache.
- If not cached → The recursive resolver (e.g., 8.8.8.8) sends queries to:
- Root DNS server → TLD (.com) server → Authoritative DNS server
- Response: IP address is returned (e.g., 93.184.216.34)
DNS Server Roles
Type | Responsibility |
---|---|
Authoritative | Holds the actual DNS records (e.g., ns1.example.com) |
Recursive | Caches responses (e.g., Google DNS 8.8.8.8) |
Tools to Test Forward Lookup
nslookup example.com
dig example.com
host example.com
Common Issues in Forward Lookup
- ❌ Misconfigured A record → Website unreachable
- ❌ Expired TTL with stale cache → Delayed updates
- ❌ DNS server unresponsive → Use
dig +trace
to debug
2. Reverse Lookup (IP → Name)
Definition
Reverse Lookup resolves an IP address (e.g., 8.8.8.8) to a domain name (e.g., dns.google).
Purpose
- Security: Spam filters verify sender IPs
- Logging: Syslogs show domain names instead of raw IPs
- Troubleshooting: Identify unknown IPs
PTR (Pointer) Record
34.216.184.93.in-addr.arpa. PTR example.com.
How Reverse Lookup Works
- Query for
8.8.8.8
- DNS resolver checks reverse zone
8.8.8.in-addr.arpa
- Authoritative server returns PTR record → e.g.,
dns.google
Reverse Lookup Zone (in-addr.arpa)
Example for 192.168.1.0/24
→ 1.168.192.in-addr.arpa
IPv6 reverse zone: .ip6.arpa
Tools to Test Reverse Lookup
nslookup 8.8.8.8
dig -x 142.250.190.46
Relationship Between A and PTR Records
Forward: example.com → 93.184.216.34
(A record)
Reverse: 34.216.184.93.in-addr.arpa → example.com
(PTR record)
🔒 Best Practice: Ensure A and PTR match to avoid email delivery issues.
Summary Table: Forward vs. Reverse Lookup
Feature | Forward Lookup | Reverse Lookup |
---|---|---|
Purpose | Resolves domain → IP | Resolves IP → domain |
Record Type | A, AAAA | PTR |
Zone Type | Forward Lookup Zone | in-addr.arpa |
Example | google.com → 8.8.8.8 | 8.8.8.8 → dns.google |
Tools | nslookup, dig | nslookup, dig -x |
Practical Examples
$ dig google.com ;; ANSWER SECTION: google.com. 300 IN A 142.250.190.46
$ dig -x 142.250.190.46 ;; ANSWER SECTION: 46.190.250.142.in-addr.arpa. 3600 IN PTR lhr25s29-in-f14.1e100.net.
Key Takeaways
- ✅ Forward Lookup = Name → IP (uses A/AAAA records)
- ✅ Reverse Lookup = IP → Name (uses PTR in .arpa zones)
- ✅ Important for web browsing, email delivery, and security
- ✅ Use tools like nslookup, dig, host for DNS testing