Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dig returns two interfaces when querying zeronsd server - any way to restrict to zerotier interface? #225

Closed
eggbean opened this issue Nov 14, 2023 · 1 comment

Comments

@eggbean
Copy link

eggbean commented Nov 14, 2023

I use a real DNS domain on all my hosts, using multiple split-horizons. On cloud instances in public and private subnets, the real domain is CNAME aliased to the public and private and domains.

This setup has been working fine for me for years, and I would prefer to keep it this way.

However, my zeronsd server, which is running on a cloud instance is giving out two IP addresses when I use dig to query it - one from the zerotier interface and another from the main interface used on its private network, as it also uses the same domain.

I know this is how DNS works, but is there a way to make it only give the address of the zerotier interface?

@eggbean
Copy link
Author

eggbean commented Nov 14, 2023

Sorry, I missed the following in the README.md:

Linux users are strongly encouraged to use systemd-networkd along with systemd-resolved to get per-interface resolvers that you can isolate to the domain you want to use. If you'd like to try something that can assist with getting you going quickly, check out the zerotier-systemd-manager repository.

@eggbean eggbean closed this as completed Nov 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant