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.

[BUG] DNS failing

See original GitHub issue

I am seeing DNS issues in the log:

2021-09-21T17:44:15.703 full_node chia.full_node.full_node: WARNING  querying DNS introducer failed: All nameservers failed to answer the query dns-introducer.chia.net. IN A: Server 192.168.0.1 UDP port 53 answered The DNS operation timed out after 1.9998652935028076 seconds; Server 192.168.0.1 UDP port 53 answered The DNS operation timed out after 1.9998807907104492 seconds; Server 192.168.0.1 UDP port 53 answered The DNS operation timed out after 1.9998843669891357 seconds; Server 192.168.0.1 UDP port 53 answered The DNS operation timed out after 1.99985933303833 seconds; Server 192.168.0.1 UDP port 53 answered SERVFAIL

Also when using dig and getent:

; <<>> DiG 9.16.20 <<>> dns-introducer.chia.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 21621
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: b3d1e510d350e8148e70c857614a5247ba0ef1e5a8429ef5 (good)
;; QUESTION SECTION:
;dns-introducer.chia.net.       IN      A

;; Query time: 4999 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Tue Sep 21 17:44:39 EDT 2021
;; MSG SIZE  rcvd: 80

Manjaro linux 5.13.15-1

It seems like I’m on ipv6, since I get an ivp6 when querying for google.com:

> getent hosts google.com                               
2607:f8b0:4008:807::200e google.com

Issue Analytics

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

github_iconTop GitHub Comments

2reactions
mariano54commented, Sep 21, 2021

I have a TPLink router. It was setting it to the default TP link DNS servers. I change to google (8.8.8.8) and cloudflare as backup. It seems to work now.

0reactions
jack60612commented, Sep 21, 2021

Looks like NetworkManager is setting this as the nameserver automatically (wired connection), is that normal?

# Generated by NetworkManager
nameserver 192.168.0.1

try telling your router to use 1.1.1.1 which is cloudflare and always works for me

Read more comments on GitHub >

github_iconTop Results From Across the Web

8 ways to fix 'DNS server not responding' errors on a Mac or PC
"DNS server not responding" errors show up when your computer and internet connection aren't communicating correctly.
Read more >
Common DNS Server Errors And How To Fix Them - TinyDNS
DNS problems usually stem from improper configuration of DNS records during most times. If you fail to put down the right values and...
Read more >
Fix your DNS problems - Computerworld
If you're having problems Web surfing, you may have a DNS problem. Here are quick ways to fix it.
Read more >
How to Resolve DNS Issues on Windows 11/10
Flush the DNS Cache and Release and Renew Your IP Address · Open the Start menu, search for Command Prompt, and select Run...
Read more >
3 Lessons from a DNS Resolution Failure Incident
The problem with this is that when a managed DNS provider has a bug, misconfiguration, or anything that could impact their service –...
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