Home / DNS / Fix DNS Resolution Timeout

DNS

Fix DNS Resolution Timeout

Resolve DNS resolution timeout issues by checking DNS servers, network connectivity, and resolver configuration.

Published: Apr 4, 20269 min readBy FixWikiHub Editorial Team

Illustration of DNS records and route checks.

Introduction

DNS resolution timeouts occur when DNS queries fail to receive responses within the expected time. Applications cannot resolve hostnames, leading to connection failures and service disruptions.

Symptoms

nslookup timeout:

```bash $ nslookup example.com

;; connection timed out; no servers could be reached ```

dig timeout:

```bash $ dig example.com

;; communications error to 8.8.8.8#53: timed out ;; no servers could be reached ```

Application error:

bash

java.net.UnknownHostException: example.com: Temporary failure in name resolution
System error: Name or service not known

curl error:

```bash $ curl https://example.com/

curl: (6) Could not resolve host: example.com ```

Common Causes

1.DNS server unreachable - DNS server down or blocked
2.Firewall blocking port 53 - UDP/TCP port 53 blocked
3.Network connectivity - Network issues preventing DNS queries
4.Wrong DNS server - Incorrect DNS server configured
5.DNS cache issues - Corrupt or stale DNS cache
6.High latency - Network latency causing timeouts

Step-by-Step Fix

Step 1: Test DNS Resolution

```bash # Test with nslookup nslookup example.com nslookup example.com 8.8.8.8

# Test with dig dig example.com dig @8.8.8.8 example.com

# Test with host host example.com host example.com 8.8.8.8

# Test specific record type dig example.com A dig example.com MX dig example.com NS

# Test with timeout dig +time=5 +tries=2 example.com

# Test reverse DNS dig -x 93.184.216.34

# Check DNS response time dig +stats example.com | grep "Query time" ```

Step 2: Check DNS Configuration

```bash # Check current DNS servers cat /etc/resolv.conf

# Typical content: # nameserver 8.8.8.8 # nameserver 8.8.4.4 # search example.com

# Check for multiple DNS servers grep nameserver /etc/resolv.conf

# Test each configured DNS server while read -r server; do echo "Testing $server:" dig @$server example.com +short +time=5 done < <(grep nameserver /etc/resolv.conf | awk '{print $2}')

# Check systemd-resolved status systemctl status systemd-resolved

# Check NetworkManager DNS nmcli dev show | grep DNS

# For Ubuntu with netplan: cat /etc/netplan/*.yaml | grep nameservers ```

Step 3: Test DNS Server Connectivity

```bash # Test if DNS port is reachable nc -uvz 8.8.8.8 53 nc -uvz 1.1.1.1 53

# Test TCP DNS (for large responses) nc -tvz 8.8.8.8 53

# Test with ping ping -c 3 8.8.8.8

# Check firewall rules iptables -L -n -v | grep 53 iptables -L -n -v | grep domain

# Allow DNS outbound iptables -I OUTPUT -p udp --dport 53 -j ACCEPT iptables -I OUTPUT -p tcp --dport 53 -j ACCEPT

# Allow DNS responses iptables -I INPUT -p udp --sport 53 -j ACCEPT iptables -I INPUT -p tcp --sport 53 -j ACCEPT

# Check ufw ufw status | grep 53 ufw allow out 53/udp ufw allow out 53/tcp ```

Step 4: Change DNS Servers

```bash # Temporary change (until reboot) echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf echo "nameserver 8.8.4.4" | sudo tee -a /etc/resolv.conf

# Or use Cloudflare DNS echo "nameserver 1.1.1.1" | sudo tee /etc/resolv.conf echo "nameserver 1.0.0.1" | sudo tee -a /etc/resolv.conf

# Permanent change - NetworkManager nmcli con mod <connection-name> ipv4.dns "8.8.8.8 8.8.4.4" nmcli con up <connection-name>

# Permanent change - netplan (Ubuntu) # Edit /etc/netplan/*.yaml network: ethernets: eth0: nameservers: addresses: [8.8.8.8, 8.8.4.4]

# Apply netplan apply

# For systemd-resolved: # Edit /etc/systemd/resolved.conf [Resolve] DNS=8.8.8.8 8.8.4.4 FallbackDNS=1.1.1.1

# Restart systemctl restart systemd-resolved ```

Step 5: Clear DNS Cache

```bash # Flush systemd-resolved cache systemd-resolve --flush-caches # Or resolvectl flush-caches

# Restart systemd-resolved systemctl restart systemd-resolved

# For nscd systemctl restart nscd nscd -i hosts

# For dnsmasq systemctl restart dnsmasq kill -HUP $(pidof dnsmasq)

# For BIND rndc flush

# Clear local application cache # Firefox: about:networking#dns > Clear DNS Cache # Chrome: chrome://net-internals/#dns > Clear host cache

# Flush Windows DNS cache ipconfig /flushdns

# Check DNS cache status systemd-resolve --statistics ```

Step 6: Check for DNS Hijacking

```bash # Check if DNS queries are being intercepted dig +short example.com @8.8.8.8 dig +short example.com @1.1.1.1

# Compare results - should be same IP

# Check for unexpected DNS responses dig example.com +trace

# Check hosts file for overrides cat /etc/hosts | grep -v "^#" | grep -v "^$"

# Remove unwanted entries # /etc/hosts should not have entries for external domains

# Check for DNS-over-HTTPS or DNS-over-TLS # These can cause issues if misconfigured systemctl status systemd-resolved | grep -i "dns over"

# Disable DoT if causing issues # In /etc/systemd/resolved.conf: DNSOverTLS=off ```

Step 7: Increase DNS Timeout

```bash # Increase timeout in /etc/resolv.conf # Add options: options timeout:10 options attempts:5 options rotate

# Full example: nameserver 8.8.8.8 nameserver 8.8.4.4 options timeout:10 attempts:5 rotate

# Test with increased timeout dig +time=10 +tries=5 example.com

# For glibc resolver (most Linux): # /etc/resolv.conf options: # timeout:n - timeout in seconds (default 5) # attempts:n - number of tries (default 2) # rotate - rotate through nameservers # single-request - disable parallel queries ```

Step 8: Debug DNS Issues

```bash # Enable DNS query logging # For systemd-resolved: resolvectl log-level debug

# Check journal for DNS logs journalctl -u systemd-resolved -f

# For BIND named: rndc querylog on tail -f /var/log/named/query.log

# Use tcpdump to capture DNS traffic tcpdump -i any port 53 -nn

# Capture to file tcpdump -i any port 53 -w dns.pcap

# Analyze with wireshark wireshark dns.pcap

# Check for DNS amplification attacks tcpdump -i any port 53 -nn | grep "A?" # Too many queries could indicate attack ```

Step 9: Set Up Local DNS Cache

```bash # Install dnsmasq apt install dnsmasq

# Configure /etc/dnsmasq.conf server=8.8.8.8 server=8.8.4.4 cache-size=1000 listen-address=127.0.0.1

# Set as local resolver echo "nameserver 127.0.0.1" > /etc/resolv.conf

# Restart dnsmasq systemctl restart dnsmasq

# Test dig example.com @127.0.0.1

# Second query should be cached (Query time: 0 msec) dig example.com @127.0.0.1

# Or use systemd-resolved caching # Already enabled by default on many systems # /etc/systemd/resolved.conf: Cache=yes ```

Step 10: Monitor DNS Performance

```bash # Create DNS monitoring script cat << 'EOF' > /usr/local/bin/check_dns.sh #!/bin/bash DOMAINS="example.com google.com github.com" DNS_SERVER="8.8.8.8"

for domain in $DOMAINS; do START=$(date +%s%N) RESULT=$(dig @$DNS_SERVER $domain +short +time=5 2>&1) END=$(date +%s%N) DURATION=$(( ($END - $START) / 1000000 ))

if [ -z "$RESULT" ]; then echo "FAIL: $domain (timeout after ${DURATION}ms)" else echo "OK: $domain (${DURATION}ms)" fi done EOF

chmod +x /usr/local/bin/check_dns.sh

# Add to cron echo "*/5 * * * * root /usr/local/bin/check_dns.sh | mail -s 'DNS Check' admin@company.com" > /etc/cron.d/dns-check

# Use Prometheus node exporter for DNS metrics # Or dnsmasq metrics ```

DNS Troubleshooting Checklist

Check	Command	Expected
DNS resolves	dig example.com	IP returned
DNS server reachable	nc -uvz 8.8.8.8 53	Connected
resolv.conf	cat /etc/resolv.conf	Valid servers
Firewall	iptables -L	Port 53 allowed
Cache	systemd-resolve --stats	Cache working

Verification

```bash # After fixing DNS configuration

# 1. Test DNS resolution dig example.com # Should return IP quickly

# 2. Check response time dig example.com | grep "Query time" # Should be < 100ms

# 3. Test all configured servers for s in $(grep nameserver /etc/resolv.conf | awk '{print $2}'); do echo "Testing $s:" dig @$s example.com +short done

# 4. Verify application connectivity curl -I https://example.com # Should connect without DNS error

# 5. Test from application # Application should resolve hostnames successfully

# 6. Monitor for recurring issues /usr/local/bin/check_dns.sh ```

Prevention

To prevent DNS resolution timeout issues from recurring, implement these proactive measures:

1. Monitor DNS Resolution Health

yaml

groups:
- name: dns-monitoring
  rules:
  - alert: DNSResolutionSlow
    expr: |
      dns_resolution_time_seconds > 1
    for: 2m
    labels:
      severity: warning
    annotations:
      summary: "DNS resolution taking longer than 1 second"

2. Configure Multiple DNS Servers

```bash # /etc/resolv.conf - Use multiple DNS servers nameserver 8.8.8.8 nameserver 8.8.4.4 nameserver 1.1.1.1

# Set timeout and retry options options timeout:2 attempts:3 rotate ```

3. Enable Local DNS Caching

bash

# Install and configure dnsmasq for local caching
apt install dnsmasq
# /etc/dnsmasq.conf:
listen-address=127.0.0.1
cache-size=1000

Best Practices Checklist

[ ] Configure multiple fallback DNS servers
[ ] Monitor DNS resolution time
[ ] Enable local DNS caching
[ ] Set appropriate timeout values
[ ] Test DNS server availability regularly
[ ] Document DNS infrastructure

[Fix DNS Server Not Responding](/articles/fix-dns-server-not-responding)
[Fix DNS Propagation Delay](/articles/fix-dns-propagation-delay)
[Fix DNS Cache Poisoning](/articles/fix-dns-cache-poisoning)

[Fix DNS Caa Record Blocking Letsencrypt Certificate Issuance Issue in DNS](dns-caa-record-blocking-letsencrypt-certificate-issuance)
[DNS CAA Record Blocking Let's Encrypt Renewal in a Multi-Provider Zone](dns-caa-record-blocking-letsencrypt-renewal-multi-provider-zone)
[Fix Dns Cdn Apex Domain Cname Restriction Alias Aname Record Issue in Dns](dns-cdn-apex-domain-cname-restriction-alias-aname-record)
[Fix DNS Cname Apex Not Supported Rfc Violation Registrar Issue in DNS](dns-cname-apex-not-supported-rfc-violation-registrar)
[Fix DNS Dnssec Validation Failure Chain Of Trust Broken Issue in DNS](dns-dnssec-validation-failure-chain-of-trust-broken)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

DNS Resolution Timeout DNS Resolution Timeout DNS DNS Resolution Timeout troubleshooting DNS Resolution Timeout fix Resolve DNS resolution timeout issues by checking DNS servers, network connectivity, and resolver configuration DNS Resolve DNS resolution timeout issues by checking DNS servers, network connectivity, and resolver configuration

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

DNS Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this dns-problems troubleshooting guide applies to my situation?

This guide is designed for dns-problems issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these dns-problems troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of dns-problems issue?

Most dns-problems issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this dns-problems issue from happening again?

Regular maintenance, monitoring, and following best practices for dns-problems configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Apr 4, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

Fix DNS Resolution Timeout

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Test DNS Resolution

Step 2: Check DNS Configuration

Step 3: Test DNS Server Connectivity

Step 4: Change DNS Servers

Step 5: Clear DNS Cache

Step 6: Check for DNS Hijacking

Step 7: Increase DNS Timeout

Step 8: Debug DNS Issues

Step 9: Set Up Local DNS Cache

Step 10: Monitor DNS Performance

DNS Troubleshooting Checklist

Verification

Prevention

1. Monitor DNS Resolution Health

2. Configure Multiple DNS Servers

3. Enable Local DNS Caching

Best Practices Checklist

People also search for

Browse Guides from Other Categories

WordPress

SSL

Cloudflare

DNS Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

Fix DNS Resolution Timeout

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Test DNS Resolution

Step 2: Check DNS Configuration

Step 3: Test DNS Server Connectivity

Step 4: Change DNS Servers

Step 5: Clear DNS Cache

Step 6: Check for DNS Hijacking

Step 7: Increase DNS Timeout

Step 8: Debug DNS Issues

Step 9: Set Up Local DNS Cache

Step 10: Monitor DNS Performance

DNS Troubleshooting Checklist

Verification

Prevention

1. Monitor DNS Resolution Health

2. Configure Multiple DNS Servers

3. Enable Local DNS Caching

Best Practices Checklist

Related Issues

Related Articles

People also search for

Share this guide

More DNS Troubleshooting Guides

Browse Guides from Other Categories

DNS Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading