-
Notifications
You must be signed in to change notification settings - Fork 56
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
can dig
but cannot ping
on debian/ubuntu
#193
Comments
dig
but cannot ping
on debian/ubuntu
If I manually change my DNS server settings to |
Hello, I think you need to run zerotier-systemd-manager on the Ubuntu 20.04 machine. Or otherwise tell it to use 172.27.27.27 for myowndomain.com. How to do this depends which of the numerous linux network manager things you're using. The android isn't working? That seems like it should work. |
android on my systems almost always requires a leave/join to trigger the dns changes. |
I do have got another more serious problem after installing zeronsd / zerotier-systemd-manager... As my home router does have a top-level public but dynamic IPV4 (but it just keeps changing every 2-3 days), I actually was always able to access (SSH) the Debian Home Server via the IPV4 (as I redirected the IPV4 to the Debian Home Server in the router's settings) After zeronsd / zerotier-systemd-manager installed and after every reboot of the server (not rebooting the home router), if I try to SSH the Debian Server from outside (not within home sub-net), sometimes I can access the server with the public IPV4 but sometimes I cannot... (and the failure rate is like much more than 50% high). Also under the failure situation with the public IPV4, I CANNOT access the server using zerotier's virtual IP... But if I SSH the Debian server from home sub-net (under the same home router) using 192.168.x.x, I can always access the Debian Home Server 100%. NOT SURE whether the system network gets stuck with zeronsd or zerotier-systemd-manager somewhere during/after reboot... Once I uninstalled zeronsd & zerotier-systemd-manager, but with zerotier-one kept, the issue above disappeared after reboot (and zerotier virtual IP works fine as before)... |
Also if the Debian Server (with |
the debian server must still run zerotier-systemd-manager. |
Yes, i meant zerotier-systemd-manager+zeronsd together when saying zeronsd as my setup was following the official instructions... Also when the problem happens, I tried to systemctl restart zerotier-systemd-manager and zeronsd, as well as restarting zerotier-one several times, but it doesn't solve the problem... The problem is completely gone only after I remove zeronsd and zerotier-systemd-manager... |
... are you running systemd-resolved? |
No. Should I?
|
read the documentation please. this isn't an interactive help forum. |
the documentation provided was well read. |
Hi, I have been using
zerotier
for a while on my private network and just started to deployzeronsd.
I followed the official zeronsd documentation as well as referring to Alan Norbauer's notes for set-up
Here are my configurations (all 3 nodes listed below are under different physical network)
myowndomain.com is my own domain registered at Godaddy.com but no public DNS settings done there (just registered).
myowndomain.com
automatically filled in Search Domain and 172.27.27.27 listed in Servers in ZeroTier Web Settings pagedig on Home Server (Debian)
dig on Office Client (Ubuntu)
Any help would be highly appreciated! Thanks!
The text was updated successfully, but these errors were encountered: