Ziti-tunnel resolver test

Quick question… as I was looking through the logs when I was starting up the ziti-router and noticed the following comment

adding ziti-tunnel.resolver.test = 19.65.28.94 to resolver

Any ideas what this is doing?

I found the following in the readme file :slight_smile:

DNS Server

ziti-tunnel runs an internal DNS server by default. The DNS server must be first in the host’s resolver
configuration (e.g. resolve.conf). A self-test is performed when ziti-tunnel starts to ensure that its
internal DNS server is configured in the system resolver:

INFO[0002] dns server started on 127.0.0.1:53           
INFO[0002] adding ziti-tunnel.resolver.test -> 19.65.28.94 to resolver 
INFO[0002] removing ziti-tunnel.resolver.test from resolver 

The test involves inserting a known hostname/IP address into the internal DNS server, and using the system
resolver to retrieve the address of the hostname. ziti-tunnel will exit if the DNS self-test fails.

Linux distributions typically manage the contents of /etc/resolv.conf, so simply editing the file
will only work for a short time until /etc/resolv.conf is overwritten by the managing process.

Is it possible to customise this?

No, it’s not configurable. What would you want to be able to configure it for? It’s added, tested for, then removed immeditely. I don’t quite see the value that you’re after

1 Like

I was just curious… any reasons why that specific IP address was used.

I don’t really have a lot of insight about these things… I noticed the IP range of 19.0.0.0 appears to link to the Ford company… hence… why I thought to ask the question

That link to ford motor company is an amazing coincidence that I was unaware of until now.

When I created the resolver self test, I chose the IP based on my first vehicle, which was a 1965 Ford Mustang with 289 cid engine and a 4-speed manual transmission.

Thanks for your curiosity!

3 Likes