Lightrun
question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DNS resolver doesn't work some times

See original GitHub issue

Expected behavior

Actual behavior

Steps to reproduce

Minimal yet complete reproducer code (or URL to code)

Netty version

4.1.34.Final

JVM version (e.g. java -version)

OS version (e.g. uname -a)

Here the output:

DatagramDnsResponse(from: /10.0.0.2:53, to: /0:0:0:0:0:0:0:0:53018, 52723, QUERY(0), NoError(0), RD RA)
DefaultDnsQuestion(useast101-rd01-0001.j2b5o9.0001.use1.cache.amazonaws.com. IN A)
DefaultDnsRawRecord(useast101-rd01-0001.j2b5o9.0001.use1.cache.amazonaws.com. 15 IN A 4B)
DefaultDnsRawRecord(OPT flags:0 udp:4096 0B)
2019-09-11 06:50:21,154-0700 [toe=00p4dqty02gn9h] [redisson-netty-2-24] DEBUG - [id: 0x9099eb92] WRITE: [58273: /10.0.0.2:53], DefaultDnsQuestion(useast101-rd01-0002.j2b5o9.0001.use1.cache.amazonaws.com. IN A)
2019-09-11 06:50:21,155-0700 [toe=00p4dqty02gn9h] [redisson-netty-2-24] DEBUG - [id: 0x9099eb92] WRITE: [31257: /10.0.0.2:53], DefaultDnsQuestion(useast101-rd01-0002.j2b5o9.0001.use1.cache.amazonaws.com. IN AAAA)
2019-09-11 06:50:21,155-0700 [toe=00p4dqty02gn9h] [redisson-netty-2-24] DEBUG - [id: 0x9099eb92] WRITE: [54664: /10.0.0.2:53], DefaultDnsQuestion(useast101-rd01-0001.j2b5o9.0001.use1.cache.amazonaws.com. IN A)
2019-09-11 06:50:22,881-0700 [toe=00p4dqty02gn9h] [redisson-netty-2-24] DEBUG - [id: 0x9099eb92] WRITE: [32392: /10.0.0.2:53], DefaultDnsQuestion(useast101-rd01-0001.j2b5o9.0001.use1.cache.amazonaws.com. IN AAAA)

2019-09-11 06:50:37,598-0700 [toe=00p4dqty02gn9h] [redisson-netty-2-24] ERROR - Unable to resolve useast101-rd01-0002.j2b5o9.0001.use1.cache.amazonaws.com io.netty.resolver.dns.DnsResolveContext$SearchDomainUnknownHostException: Search domain query failed. Original hostname: 'useast101-rd01-0002.j2b5o9.0001.use1.cache.amazonaws.com' failed to resolve 'useast101-rd01-0002.j2b5o9.0001.use1.cache.amazonaws.com' after 2 queries
at io.netty.resolver.dns.DnsResolveContext.finishResolve(DnsResolveContext.java:877) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsResolveContext.tryToFinishResolve(DnsResolveContext.java:838) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsResolveContext.query(DnsResolveContext.java:333) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsResolveContext.access$600(DnsResolveContext.java:63) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsResolveContext$3.operationComplete(DnsResolveContext.java:382) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:502) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:495) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:474) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:415) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:540) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:533) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:114) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.resolver.dns.DnsQueryContext.setFailure(DnsQueryContext.java:220) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsQueryContext.access$300(DnsQueryContext.java:43) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsQueryContext$4.run(DnsQueryContext.java:170) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:127) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:405) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) [netty-transport-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:906) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
Caused by: io.netty.resolver.dns.DnsNameResolverTimeoutException: [/10.0.0.2:53] query timed out after 5000 milliseconds (no stack trace available)

2019-09-11 06:51:13,388-0700 [toe=00p4dqty02gn9h] [redisson-netty-2-24] ERROR - Unable to resolve useast101-rd01-0001.j2b5o9.0001.use1.cache.amazonaws.com io.netty.resolver.dns.DnsResolveContext$SearchDomainUnknownHostException: Search domain query failed. Original hostname: 'useast101-rd01-0001.j2b5o9.0001.use1.cache.amazonaws.com' failed to resolve 'useast101-rd01-0001.j2b5o9.0001.use1.cache.amazonaws.com' after 2 queries
at io.netty.resolver.dns.DnsResolveContext.finishResolve(DnsResolveContext.java:877) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsResolveContext.tryToFinishResolve(DnsResolveContext.java:838) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsResolveContext.query(DnsResolveContext.java:333) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsResolveContext.access$600(DnsResolveContext.java:63) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsResolveContext$3.operationComplete(DnsResolveContext.java:382) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:502) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:495) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:474) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:415) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:540) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:533) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:114) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.resolver.dns.DnsQueryContext.setFailure(DnsQueryContext.java:220) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsQueryContext.access$300(DnsQueryContext.java:43) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.resolver.dns.DnsQueryContext$4.run(DnsQueryContext.java:170) [netty-resolver-dns-4.1.34.Final.jar:4.1.34.Final]
at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:127) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:405) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) [netty-transport-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:906) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.35.Final.jar:4.1.35.Final]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
Caused by: io.netty.resolver.dns.DnsNameResolverTimeoutException: [/10.0.0.2:53] query timed out after 5000 milliseconds (no stack trace available)

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
vietjcommented, Mar 18, 2020

we have a similar concern reported in our tracker that sporadically fails and the error seems to be related to the presence of the OPT record in the server response: https://github.com/eclipse-vertx/vert.x/issues/3150

0reactions
mrnikocommented, Nov 14, 2019

@normanmaurer

Here is the log output for this issue:

07:39:58.566[redisson-netty-2-14] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x7d835670] WRITE: UDP, [40490: /127.0.0.11:53], DefaultDnsQuestion(redis-master. IN A)
07:39:58.569[redisson-netty-2-14] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x7d835670] RECEIVED: UDP [40490: /127.0.0.11:53], DatagramDnsResponse(from: /127.0.0.11:53, to: /0.0.0.0:53290, 40490, QUERY(0), NXDomain(3), RD RA)
        DefaultDnsQuestion(redis-master. IN A)
        DefaultDnsRawRecord(. 4277 IN SOA 64B)
        DefaultDnsRawRecord(OPT flags:0 udp:4096 0B)
07:39:58.569[redisson-netty-2-14] DEBUG i.netty.resolver.dns.DnsQueryContext - [id: 0x7d835670] WRITE: UDP, [15257: /127.0.0.11:53], DefaultDnsQuestion(redis-master. IN CNAME)
07:39:58.575[redisson-netty-2-14] DEBUG i.netty.resolver.dns.DnsNameResolver - [id: 0x7d835670] RECEIVED: UDP [15257: /127.0.0.11:53], DatagramDnsResponse(from: /127.0.0.11:53, to: /0.0.0.0:53290, 15257, QUERY(0), NXDomain(3), RD RA)
        DefaultDnsQuestion(redis-master. IN CNAME)
        DefaultDnsRawRecord(. 4277 IN SOA 64B)
        DefaultDnsRawRecord(OPT flags:0 udp:4096 0B)
07:39:58.575[redisson-netty-2-14] ERROR o.r.c.ReplicatedConnectionManager - failed to resolve 'redis-master' after 2 queries
java.net.UnknownHostException: failed to resolve 'redis-master' after 2 queries
Read more comments on GitHub >

github_iconTop Results From Across the Web

How to the Fix "DNS Server Not Responding" Error - Kinsta®
“DNS Server Not Responding” means that your browser was unable to establish a connection to the internet. Typically, DNS errors are caused by ......
Read more >
8 ways to fix 'DNS server not responding' errors on a Mac or PC
Open the Control Panel and click Network and Internet, then Network and Sharing Center, and then Change adapter settings. 2. Right-click on your ......
Read more >
How to Fix 'The DNS Server isn't responding' error [100 ...
Solution 4: Restart your modem and router. If your modem or router doesn't work properly, the DNS server could stop responding, either. You...
Read more >
DNS works sometimes, but sometimes it doesn't. What can we ...
Replication issues can cause intermittent problems in Active Directory (AD)-integrated DNS zones. Ensure that AD replication is working properly to start with.
Read more >
How To Fix 'DNS Server Not Responding' Error On Windows 10
Sometimes there's a lot of data traffic on a router which generates this issue of the DNS server not responding. There is an...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

DNS Resolver leaking direct memory

Next page

How can we close gap on client performance vs blocking sockets?