Open clehner opened 2 years ago
Greetings, Talked about also in #157 , I'm putting here an example of resolving that works. Please let me know if otherwise
$ nslookup mail.mesh.nycmesh.net 199.167.59.10
Server: 199.167.59.10
Address: 199.167.59.10#53
Non-authoritative answer:
Name: mail.mesh.nycmesh.net
Address: 10.70.140.70
$ nslookup google.com 199.167.59.10
Server: 199.167.59.10
Address: 199.167.59.10#53
Non-authoritative answer:
Name: google.com
Address: 142.250.80.78
Name: google.com
Address: 2607:f8b0:4006:80c::200e
nslookup mail.mesh.nycmesh.net 199.167.59.10 [...]
I see these resolutions working only from within the mesh.
I am still finding that 199.167.59.10 is unreachable outside the mesh. From two networks, pinging it results in Destination Net Unreachable from 206.82.104.151. From other networks I get no response.
However, I find that changing 10 to 11 works. 199.167.59.11 appears to be a functioning public resolver for mesh.nycmesh.net (including for .mesh TLD). Perhaps the docs should be updated to use that address instead?
The DNS page lists a public IP address for a DNS server: https://github.com/nycmeshnet/docs/blob/6ed7b1cea987f333d2c919e611c4255408bac978/content/networking/dns.md#top-level-domains
I see the host
199.167.59.10
answers DNS queries from inside the mesh, including for the.mesh
TLD. However, I don't find it to be reachable from outside the mesh - via DNS queries or pings. Here is traceroute info from a DigitalOcean NYC3 VPS:Possible fixes for this issue:
199.167.59.10
is only for use in the mesh (and/or other specific networks?)199.167.59.10
to respond to DNS queries from outside the mesh.