Open Opensourcecommunitydevelopment opened 8 years ago
i looked up native-dns and it shows that if listening Online IIPV6 it needs
Server creation
createServer and createUDPServer -- both create a UDP based server, they accept an optional object for configuration,
{ dgram_type: 'udp4' } is the default option, the other is udp6
hello,
i found this helpful. But i experienced problems if trying To bind v6dns On IPv6 localhost.
But Version 4 works Fine:
PS C:\> v6dns 127.0.0.1 53 ::1 653 6 v6dns 1.0.5 Lovely presented by adamyi. Under MIT License. Using configuration: { host: '127.0.0.1', port: 53, server: '::1', serverport: 653, priority: 6 } server listening on { address: '127.0.0.1', family: 'IPv4', port: 53 } server listening on { address: '127.0.0.1', family: 'IPv4', port: 53 }
With the erros above, i still can query Version 6dns over tcp locally On [::1]:53 ! But udp Not. No the port is Not inuse and nodejs got admin privilege. At the first Look, for me it looks like the „:" port Argument is Not escaped correctly ? How Comes TCP listening works with same Version6dns arguments
If using „current“ node Version it gives this error: