Executing Manual DNS Query Resolution using dig and nslookup
When you update a domain's DNS records, the changes aren't instantaneous due to Time-to-Live (TTL) values and global propagation. To diagnose resolution failures or verify that your Hovixa VPS is pointing to the correct IP, you need tools that query the Domain Name System directly. While nslookup is a legacy standard, dig (Domain Information Groper) is the preferred choice for sysadmins due to its detailed output and flexibility.
1. The DNS Resolution Workflow
Before querying, it's vital to understand how a recursive resolver fetches your data. If your local machine shows an old IP but dig shows the new one, the issue is local caching, not the server.
2. Advanced Querying with dig
dig is part of the BIND utilities. Its primary strength is the "Answer Section," which provides the raw data returned by the name server.
Basic Syntax:
# Query for the A record (IP address)
dig hovixa.com
# Query a specific record type (MX for mail, TXT for SPF)
dig hovixa.com MX
Querying a Specific Name Server:
To bypass your ISP's cache and see what the world sees, query a public resolver like Google (8.8.8.8) or Cloudflare (1.1.1.1):
dig @8.8.8.8 hovixa.com
3. Legacy Troubleshooting with nslookup
nslookup is often pre-installed on both Linux and Windows. It operates in two modes: non-interactive (single command) and interactive (shell).
# Non-interactive query
nslookup hovixa.com
# Interactive mode
nslookup
> server 1.1.1.1
> set type=TXT
> hovixa.com
4. DNS Record Diagnostic Matrix
| Record Type | Query Purpose | dig Command |
|---|---|---|
| A | Verify IPv4 address of the VPS. | `dig hovixa.com A` |
| AAAA | Verify IPv6 address. | `dig hovixa.com AAAA` |
| CNAME | Check alias (e.g., www to root). | `dig www.hovixa.com CNAME` |
| MX | Confirm where email is routed. | `dig hovixa.com MX` |
| TXT | Validate SPF, DKIM, or DMARC. | `dig hovixa.com TXT` |
5. Technical Implementation Details
- +short Flag: If you only need the IP address without the verbose headers, use
dig hovixa.com +short. This is excellent for use in bash scripts. - TTL (Time to Live): The second column in a
diganswer section shows the remaining TTL in seconds. If this number is high, your changes will take longer to appear in caches. - Reverse DNS (PTR): To see which domain is associated with an IP (crucial for email deliverability), use the
-xflag:dig -x 1.2.3.4.
Sysadmin Advice: Use dig +trace hovixa.com to follow the query from the root servers down to the authoritative name server. This is the fastest way to identify exactly where a DNS "break" is occurring in the chain.
