IPv6 not supported by DNS
See original GitHub issueCannot discover devices. The log contains an unsettling comment:
dynamic.go:65 ... failed to lookup dynamic relays ... dial tcp: lookup relays.syncthing.net on 1111:2222:3333::33:53: dial udp: too many colons in address 1111:2222:3333::33:53:
(It’s the DNS server’s ipv6 address.)
Version Information
App Version: 0.9.2
Syncthing Version: v0.14.14
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Fixing DNS issues which are caused by non functional IPv6 ...
First iterate through the LAN adapters in the Network and Sharing Center and check in the Properties of each of them if IPv6...
Read more >IPv6 DNS: Understanding IPv6 and a Quick Implementation ...
We explain IPv6's slow adoption, and how to support IPv6 in your DNS server. ... is currently not IPv6 capable and therefore cannot...
Read more >DNS issues on the network while IPv6 enabled on clients
Hi,. I'm experiencing network issues possibly caused by some IPv6 misconfiguration. I have a Windows Server 2012 R2 Standard server which is ...
Read more >How to diagnose why IPv6 is not supported - Super User
If you don't have an IPv6 address, check whether your router does (both on its WAN and LAN interfaces). It needs to get...
Read more >Does DNS Support IPv6? - 华为云
Does DNS Support IPv6? ... DNS can translate domain names to both IPv4 and IPv6 addresses. To translate a domain name to an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The issue here is the patch to fix Go DNS on Android not handling v6 DNS servers
Fixed in #853.