-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Open
Labels
P2should be fixed if one has timeshould be fixed if one has timebeginnerIssues suitable for new developersIssues suitable for new developersbugUnintended code behaviourUnintended code behaviourgood first issueIssues suitable for first time contributors to LNDIssues suitable for first time contributors to LNDnode-managementp2pCode related to the peer-to-peer behaviourCode related to the peer-to-peer behaviour
Description
Background
Describe your issue here.
Your environment
- version of
lnd
0.17.3 - which operating system (
uname -a
on *Nix) ubuntu 20.04 - version of
btcd
,bitcoind
, or other backend - any other relevant environment details
Steps to reproduce
I run a node that I want accessible via clearnet IPv4, IPv6 and Tor.
I have a domain lightning.foo.com
that has both A and AAAA DNS records. When I set this in lnd.conf
externalhosts=lightning.foo.com
The node advertises only IPv4 and Tor (as checked via getinfo
)
Expected behaviour
If a domain resolves to both IPv4 and IPv6 lnd should advertise both protocols
Actual behaviour
The node favors one of the protocols. I guess this code does the resolve on the first interface
Line 1644 in 613bfc0
cfg.net.ResolveTCPAddr, |
thiagorb
Metadata
Metadata
Assignees
Labels
P2should be fixed if one has timeshould be fixed if one has timebeginnerIssues suitable for new developersIssues suitable for new developersbugUnintended code behaviourUnintended code behaviourgood first issueIssues suitable for first time contributors to LNDIssues suitable for first time contributors to LNDnode-managementp2pCode related to the peer-to-peer behaviourCode related to the peer-to-peer behaviour