Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Troubleshooting

Linux DNS troubleshooting: test resolver, network and authoritative answers

Published August 2026 · 2 min read · Updated 2026-09-05

Linux DNS troubleshooting should separate local resolver configuration, recursive resolution, authoritative DNS, and application-specific caching. “DNS is broken” can mean the server cannot reach a resolver, a hostname is genuinely misconfigured, or one process is holding stale data.

Test the resolver the server actually uses

Inspect resolv.conf or the active systemd-resolved/network configuration and query the configured resolver. Compare with a known public recursive resolver to determine whether the issue follows one resolver path.

A local caching daemon or container runtime may use a different resolver than the host shell.

Query authoritative data when ownership matters

For a domain you control, trace delegation and ask the authoritative nameservers directly. If authoritative data is wrong, changing the VPS resolver will not fix public DNS.

Record TTLs and serials during recent changes so stale recursive answers are not confused with authoritative inconsistency.

Check network and protocol reachability

DNS normally uses UDP and can fall back to TCP. Firewalls, VPN routing, broken IPv6 paths, or provider policy can make a configured resolver unreachable even when other internet access works.

Test both name resolution and direct IP connectivity to separate DNS from the application’s destination network.

Inspect application caches and search domains

Browsers, runtimes, JVMs, containers, and applications may cache results or append search domains. Restart or flush only the relevant cache after proving it is stale.

  • Inspect the active resolver.
  • Compare recursive and authoritative answers.
  • Check UDP/TCP reachability.
  • Account for application-level caches.

Next step

Separate local resolver failures from upstream DNS, routing and authoritative-zone problems using direct queries and the system resolver configuration.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move