lnd: Crash during startup on lookup soa.nodes.lighning.directory: server misbehaving

Background

My lnd started crashing after updating to master. Before this update I was running git master from few days ago and didn’t experience such problem.

Lnd crashes directly on startup with the line:

lookup soa.nodes.lightning.directory on 192.168.69.1:53: server misbehaving (that IP is my router)

I tested latest release lnd-v0.4.2-beta and everything works normally. So I expect something wrong has been commited to master recently.

Your environment

git master c344a3a642b9a8dc8303d7f6b4bd130d7eb747f5
Linux server01 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux
bitcoind 0.16.1

Steps to reproduce

# ./lnd
lookup soa.nodes.lightning.directory on 192.168.69.1:53: server misbehaving

Expected behaviour

Node should start normally.

Actual behaviour

Process exits.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 22 (7 by maintainers)

Most upvoted comments

Seems like cloudflare dns (1.1.1.1) doens’t resolve:

dig soa.nodes.lightning.directory @1.1.1.1

; <<>> DiG 9.10.6 <<>> soa.nodes.lightning.directory @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 40711
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;soa.nodes.lightning.directory.	IN	A

;; Query time: 4134 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Jul 10 12:11:32 CEST 2018
;; MSG SIZE  rcvd: 58

ediskraba1@edismacbook:~$ dig soa.nodes.lightni

The Google DNS does resolve.

I think it’s a problem with the nodes.lightning.directory DNS server configuration:

NS for .directory > demand.alpha.aridns.net.au.

> dig ns lightning.directory @demand.alpha.aridns.net.au.
...
;; AUTHORITY SECTION:
lightning.directory.	86400	IN	NS	nodes.lightning.directory.
lightning.directory.	86400	IN	NS	nodes2.lightning.directory.

;; ADDITIONAL SECTION:
nodes.lightning.directory. 86400 IN	A	104.131.26.124
nodes2.lightning.directory. 86400 IN	A	104.131.26.124

> dig soa lightning.directory @104.131.26.124
; <<>> DiG 9.10.6 <<>> soa lightning.directory @104.131.26.124
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 18450
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;lightning.directory.		IN	SOA

;; Query time: 175 msec
;; SERVER: 104.131.26.124#53(104.131.26.124)
;; WHEN: Tue Jul 10 12:31:12 CEST 2018
;; MSG SIZE  rcvd: 37

no SOA configured for lightning.directory.

edspiner on Jul 10, 2018

Had to reboot the server, but generally it should boot if it’s down, fixing it shortly in a new commit. Apologies for the issue.

On Thu, Aug 16, 2018, 7:53 PM Alexey Zagarin notifications@github.com wrote:

@Roasbeef https://github.com/Roasbeef I’m having the same problem, maybe we should reopen the issue? For me, neither Google nor Cloudfare working. There might be something wrong with nodes.lightning.directory DNS config as @edspiner https://github.com/edspiner pointed.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/lightningnetwork/lnd/issues/1463#issuecomment-413742962, or mute the thread https://github.com/notifications/unsubscribe-auth/AA87LnHextReXEoxwoMyIP8C9T59u8xzks5uRjAzgaJpZM4U7l5q .

Roasbeef on Aug 17, 2018