Opensourcecommunitydevelopment

there exists a visual studio port but dated a few versions (years) back that support IPv6 on Windows

yes on high latency it defaults to ipv4 sadly. chrome works well for you? i sometimes get ERR_NAME_RESOLUTION_FAILED from chrome because it continues query A record and v6dns does reply...

i found a working solution for me with chrome and Force Internet Protocol Version 6 if you don't mind To use google public dns this may work for you too....

Okay, i have uploaded a Version with preferIPv6 of other nodejs resolver i do like To reference you to here: https://github.com/Opensourcecommunitydevelopment/dns-over-http2 it will always resolve AAAA/IPv6 if available. But if...

tHe whole query String should be eQual size. `` getPaddedStr(259-len(qname)-len(string(qtype))))`` ???len???? resolving github.com./TXT len %!s(int=16) 1 resolving github.com./ANY len %!s(int=255) 2 resolving github.com./A len %!s(int=1) 1

Makes Sense, for less configuration, if No subnet specified, google Domain Name Server/Service/Scheme/System guesses which is the nearest for you. Depending On the IP Protocol Version the Query is done...

**socks5** would be useful :-) depending on fireWALL quic could be worse, since User Datagram Protocol (Internet) is Not permitted more commonly i believe

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...

you Are correct. http/2 would greatly reduce latency here