Home / DNS / Fix DNS Resolution Timeout Randomly

DNS

Fix DNS Resolution Timeout Randomly

Resolve intermittent DNS resolution timeouts by checking resolver configuration, network connectivity, and DNS server health.

Published: Apr 5, 202610 min readBy FixWikiHub Editorial Team

Illustration of DNS records and route checks.

Introduction

DNS resolution intermittently times out, causing applications to fail connecting to services. Some queries succeed while others fail without a clear pattern, affecting system reliability.

Symptoms

Intermittent DNS failure:

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

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

# Try again: $ curl https://example.com # Works fine ```

nslookup timeout:

```bash $ nslookup example.com

;; connection timed out; no servers could be reached

# Second attempt: $ nslookup example.com Server: 8.8.8.8 Address: 8.8.8.8#53

Non-authoritative answer: Name: example.com Address: 93.184.216.34 ```

Application errors:

bash

# In application logs:
java.net.UnknownHostException: api.example.com: Name or service not known
# or
getaddrinfo failed: Temporary failure in name resolution

Common Causes

1.DNS server overload - Server cannot handle query volume
2.Network packet loss - UDP packets dropped
3.Firewall rules - Intermittently blocking DNS
4.DNS server unreachable - Temporary connectivity issues
5.Resolver cache issues - Local resolver problems
6.Multiple DNS servers misconfigured - Failover not working

Step-by-Step Fix

Step 1: Check Current DNS Configuration

```bash # Check resolver configuration cat /etc/resolv.conf

# Check for multiple nameservers grep nameserver /etc/resolv.conf

# Check search domains grep search /etc/resolv.conf

# Check DNS options grep options /etc/resolv.conf

# Check systemd-resolved status systemctl status systemd-resolved

# Check NetworkManager DNS nmcli dev show | grep DNS

# Check if using local DNS cache ps aux | grep -E "dnsmasq|unbound|systemd-resolve" ```

Step 2: Test DNS Resolution

```bash # Test with dig (shows timing) dig example.com

# Test specific DNS server dig @8.8.8.8 example.com

# Test with timing info dig +stats example.com

# Query statistics: ;; Query time: 50 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Wed Apr 16 00:59:00 UTC 2026 ;; MSG SIZE rcvd: 56

# Test with nslookup nslookup example.com 8.8.8.8

# Test with host host example.com 8.8.8.8

# Test UDP connectivity nc -uzv 8.8.8.8 53

# Test TCP DNS (for large responses) dig +tcp @8.8.8.8 example.com ```

Step 3: Run Continuous DNS Tests

```bash # Continuous DNS monitoring while true; do echo "$(date): $(dig +short @8.8.8.8 example.com 2>&1)" sleep 1 done

# Track success/failure rate cat << 'EOF' > dns_test.sh #!/bin/bash SERVER=8.8.8.8 DOMAIN=example.com COUNT=100 SUCCESS=0 FAIL=0

for i in $(seq 1 $COUNT); do RESULT=$(dig +short +time=2 @$SERVER $DOMAIN 2>&1) if [ -n "$RESULT" ]; then ((SUCCESS++)) echo -n "." else ((FAIL++)) echo -n "X" fi done

echo "" echo "Success: $SUCCESS/$COUNT" echo "Failed: $FAIL/$COUNT" echo "Success rate: $(echo "scale=2; $SUCCESS*100/$COUNT" | bc)%" EOF

chmod +x dns_test.sh ./dns_test.sh

# Test all configured nameservers for ns in $(grep nameserver /etc/resolv.conf | awk '{print $2}'); do echo "Testing $ns..." for i in {1..10}; do dig +short +time=2 @$ns google.com >/dev/null && echo -n "." || echo -n "X" done echo "" done ```

Step 4: Check DNS Server Health

```bash # Check if DNS servers are responding for ns in 8.8.8.8 8.8.4.4; do echo "Testing $ns:" ping -c 5 $ns echo "" done

# Check DNS server latency for ns in 8.8.8.8 8.8.4.4; do echo "Latency to $ns:" for i in {1..10}; do time dig +short @$ns example.com >/dev/null 2>&1 done done

# Check if using IPv6 DNS (may have issues) dig @2001:4860:4860::8888 example.com

# Test public vs private DNS time dig @8.8.8.8 example.com time dig @192.168.1.1 example.com # Local DNS ```

Step 5: Check Network for Packet Loss

```bash # Check for packet loss to DNS servers mtr -c 100 -r 8.8.8.8

# Check interface errors ip -s link show eth0

# Look for: # RX errors, dropped, overruns # TX errors, carrier

# Check for UDP packet drops netstat -su | grep -A 5 Udp

# Check for dropped packets cat /proc/net/snmp | grep Udp

# Check firewall drops iptables -L -n -v | grep -i drop

# Monitor packet loss in real-time watch -n 1 'netstat -su | grep -E "packet receive errors|buffer errors"' ```

Step 6: Configure DNS Timeouts and Retries

```bash # Edit /etc/resolv.conf to add options:

# Increase timeout (default 5 seconds per attempt) options timeout:10

# Increase attempts (default 2) options attempts:5

# Combine options options timeout:10 attempts:5

# Rotate between nameservers options rotate

# Use EDNS0 for larger responses options edns0

# Single-request (avoid parallel queries) options single-request

# Single-request-reopen (new socket per query) options single-request-reopen

# Complete example: nameserver 8.8.8.8 nameserver 8.8.4.4 nameserver 1.1.1.1 options timeout:5 attempts:3 rotate

# For systemd-resolved, edit: # /etc/systemd/resolved.conf [Resolve] DNS=8.8.8.8 8.8.4.4 1.1.1.1 FallbackDNS=1.0.0.1 DNSStubListener=yes ReadEtcHosts=yes

# Restart systemd-resolved systemctl restart systemd-resolved ```

Step 7: Add Backup DNS Servers

```bash # Add multiple DNS servers for redundancy

# In /etc/resolv.conf: nameserver 8.8.8.8 # Google primary nameserver 8.8.4.4 # Google secondary nameserver 1.1.1.1 # Cloudflare primary nameserver 1.0.0.1 # Cloudflare secondary

# With rotation for load balancing: options rotate timeout:2 attempts:2

# For NetworkManager: nmcli con mod eth0 ipv4.dns "8.8.8.8 8.8.4.4 1.1.1.1" nmcli con up eth0

# Verify changes cat /etc/resolv.conf ```

Step 8: Set Up Local DNS Cache

```bash # Install dnsmasq for local caching apt-get install dnsmasq # Ubuntu/Debian yum install dnsmasq # CentOS/RHEL

# Configure dnsmasq cat << 'EOF' > /etc/dnsmasq.conf # Use upstream DNS servers server=8.8.8.8 server=8.8.4.4 server=1.1.1.1

# Cache size cache-size=1000

# Cache TTL min-cache-ttl=60 max-cache-ttl=3600

# Listen on localhost listen-address=127.0.0.1 bind-interfaces

# Log queries (for debugging) # log-queries EOF

# Start dnsmasq systemctl enable dnsmasq systemctl start dnsmasq

# Update resolv.conf to use local cache echo "nameserver 127.0.0.1" > /etc/resolv.conf echo "options timeout:2 attempts:2" >> /etc/resolv.conf

# Test cache dig @127.0.0.1 example.com # First query: ~50ms dig @127.0.0.1 example.com # Second query: ~1ms (cached) ```

Step 9: Check Application DNS Settings

```bash # Java applications # Add to JVM options: -Dsun.net.inetaddr.ttl=30 -Dsun.net.inetaddr.negative.ttl=10

# Or in java.security: networkaddress.cache.ttl=30 networkaddress.cache.negative.ttl=10

# Python applications # Use dnspython for explicit DNS: import dns.resolver resolver = dns.resolver.Resolver() resolver.nameservers = ['8.8.8.8', '1.1.1.1'] resolver.timeout = 5 resolver.lifetime = 10 answer = resolver.resolve('example.com', 'A')

# Node.js applications # Set DNS servers: const dns = require('dns'); dns.setServers(['8.8.8.8', '8.8.4.4']);

# glibc resolver options # In /etc/resolv.conf: options timeout:5 attempts:3 rotate ```

Step 10: Monitor DNS Resolution

```bash # Create monitoring script cat << 'EOF' > monitor_dns.sh #!/bin/bash

echo "=== DNS Configuration ===" cat /etc/resolv.conf

echo "" echo "=== DNS Server Latency ===" for ns in $(grep nameserver /etc/resolv.conf | awk '{print $2}'); do echo -n "$ns: " avg=$(for i in {1..5}; do dig +short @$ns google.com 2>/dev/null | head -1 && echo "ok" || echo "fail"; done | grep -c ok) echo "$avg/5 successful" done

echo "" echo "=== Recent DNS Failures ===" journalctl -u systemd-resolved --since "1 hour ago" | grep -i "fail|error|timeout" | tail -10

echo "" echo "=== DNS Cache Stats (dnsmasq) ===" if pgrep dnsmasq >/dev/null; then echo "Cache size: $(sudo dnsmasq --dump-cache 2>/dev/null | wc -l)" sudo kill -USR1 $(cat /var/run/dnsmasq/dnsmasq.pid) fi

echo "" echo "=== UDP Statistics ===" cat /proc/net/snmp | grep Udp EOF

chmod +x monitor_dns.sh

# Set up continuous monitoring watch -n 10 ./monitor_dns.sh

# Prometheus node exporter DNS monitoring # Add to prometheus alerts: - alert: DNSResolutionFailure expr: probe_success{job="dns_probe"} == 0 for: 2m labels: severity: critical annotations: summary: "DNS resolution failing" EOF ```

DNS Resolution Timeout Checklist

Check	Command	Expected
Resolver config	cat /etc/resolv.conf	Valid nameservers
DNS response	dig @server domain	Returns IP
Latency	dig +stats	< 100ms typical
Packet loss	mtr dns-server	< 1%
Multiple servers	grep nameserver	2+ servers
Timeout options	grep options	timeout >= 5
Local cache	ps aux \	grep dnsmasq	Running

Verification

```bash # After adjusting DNS configuration

# 1. Test consistent resolution for i in {1..20}; do dig +short google.com; done // All queries return same IP

# 2. Measure response times for i in {1..20}; do time dig +short google.com; done 2>&1 | grep real // Consistent low latency

# 3. Test all configured servers for ns in $(grep nameserver /etc/resolv.conf | awk '{print $2}'); do echo "Testing $ns:" for i in {1..5}; do dig +short @$ns google.com || echo "FAIL"; done done // All servers respond

# 4. Monitor for failures timeout 60 bash -c 'while true; do dig +short google.com || echo "FAIL at $(date)"; sleep 1; done' // No failures for 60 seconds

# 5. Check application connectivity curl -I https://google.com // Connects successfully ```

Prevention

To prevent random DNS resolution timeouts from recurring, implement these proactive measures:

1. Configure Multiple DNS Servers

bash

# In /etc/resolv.conf:
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 1.1.1.1
options timeout:2 attempts:3 rotate

2. Enable DNS Caching

```bash # Install and configure dnsmasq for local caching apt-get install dnsmasq

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

systemctl enable dnsmasq systemctl start dnsmasq ```

3. Set Up DNS Monitoring

yaml

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

4. Implement DNS Health Checks

```bash # DNS health monitoring script cat << 'EOF' > /usr/local/bin/monitor_dns.sh #!/bin/bash DNS_SERVERS=("8.8.8.8" "8.8.4.4" "1.1.1.1") TEST_DOMAINS=("google.com" "github.com")

for server in "${DNS_SERVERS[@]}"; do for domain in "${TEST_DOMAINS[@]}"; do dig @$server $domain +short +time=2 || echo "FAIL: $server" done done EOF

chmod +x /usr/local/bin/monitor_dns.sh ```

5. Use DNS over HTTPS/TLS

```bash # Configure DNS over HTTPS apt-get install stubby

# /etc/stubby/stubby.yml: upstream_recursive_servers: - address_data: 8.8.8.8 tls_port: 853 tls_auth_name: "dns.google"

systemctl enable stubby ```

Best Practices Checklist

[ ] Configure multiple DNS servers
[ ] Enable local DNS caching
[ ] Monitor DNS resolution with alerts
[ ] Run regular DNS health checks
[ ] Implement application-level retries
[ ] Consider DNS over HTTPS/TLS
[ ] Test DNS failover scenarios

[Fix DNS Resolution Failed](/articles/fix-dns-resolution-failed)
[Fix DNS Server Not Responding](/articles/fix-dns-server-not-responding)
[Fix DNS Propagation Delay](/articles/fix-dns-propagation-delay)

[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 Randomly DNS Resolution Timeout Randomly DNS DNS Resolution Timeout Randomly troubleshooting DNS Resolution Timeout Randomly fix Resolve intermittent DNS resolution timeouts by checking resolver configuration, network connectivity, and DNS server health DNS Resolve intermittent DNS resolution timeouts by checking resolver configuration, network connectivity, and DNS server health

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 5, 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 Randomly

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Current DNS Configuration

Step 2: Test DNS Resolution

Step 3: Run Continuous DNS Tests

Step 4: Check DNS Server Health

Step 5: Check Network for Packet Loss

Step 6: Configure DNS Timeouts and Retries

Step 7: Add Backup DNS Servers

Step 8: Set Up Local DNS Cache

Step 9: Check Application DNS Settings

Step 10: Monitor DNS Resolution

DNS Resolution Timeout Checklist

Verification

Prevention

1. Configure Multiple DNS Servers

2. Enable DNS Caching

3. Set Up DNS Monitoring

4. Implement DNS Health Checks

5. Use DNS over HTTPS/TLS

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 Randomly

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Step 1: Check Current DNS Configuration

Step 2: Test DNS Resolution

Step 3: Run Continuous DNS Tests

Step 4: Check DNS Server Health

Step 5: Check Network for Packet Loss

Step 6: Configure DNS Timeouts and Retries

Step 7: Add Backup DNS Servers

Step 8: Set Up Local DNS Cache

Step 9: Check Application DNS Settings

Step 10: Monitor DNS Resolution

DNS Resolution Timeout Checklist

Verification

Prevention

1. Configure Multiple DNS Servers

2. Enable DNS Caching

3. Set Up DNS Monitoring

4. Implement DNS Health Checks

5. Use DNS over HTTPS/TLS

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