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
199.167.59.10 - Public DNS Resolver for anyone in the world. No Logs, No filtering.
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:
traceroute to 199.167.59.10 (199.167.59.10), 30 hops max, 60 byte packets
1 * * *
2 10.74.7.40 (10.74.7.40) 1.166 ms 10.74.7.46 (10.74.7.46) 1.150 ms 10.74.7.38 (10.74.7.38) 1.134 ms
3 138.197.248.250 (138.197.248.250) 1.531 ms 1.873 ms 138.197.248.238 (138.197.248.238) 1.688 ms
4 138.197.248.54 (138.197.248.54) 1.546 ms 138.197.248.56 (138.197.248.56) 1.558 ms 138.197.248.58 (138.197.248.58) 1.634 ms
5 138.197.244.40 (138.197.244.40) 1.789 ms 1.772 ms 1.756 ms
6 375pearl.nycmesh.net (206.82.104.151) 1.905 ms !N 1.088 ms !N *
Possible fixes for this issue:
- Update the page to clarify that
199.167.59.10 is only for use in the mesh (and/or other specific networks?)
- Enable
199.167.59.10 to respond to DNS queries from outside the mesh.
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.10answers DNS queries from inside the mesh, including for the.meshTLD. 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.10is only for use in the mesh (and/or other specific networks?)199.167.59.10to respond to DNS queries from outside the mesh.