NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Unable to use local DNS server
As a home user, I want to have a good DNS for my local network. I decided to install PowerDNS on one of my virtual machines. It works perfectly well and does exactly what I need; resolve local names...
Forgot to reload systemd (I'm still pretty new to this)
So, I did a:
root@truck # systemctl daemon-reload
root@truck # systemctl restart connmanand got PowerDNS working.
Thanks for all the help. ;-))
I read a discussion about connmand about port 53 that it uses which told to edit the following line in /etc//systemd/system/multi-user.target.wants/connman.service :
ExecStart=/usr/sbin/connmand -n
should become:
ExecStart=/usr/sbin/connmand -n --nodnsproxy
I did this and restarted connmand with: systemctl restart connman
Inspection of /proc/<PID>/cmdline learned me it didn't use the '--nodnsproxy' however.
...but I get the feeling I'm getting close. :-)
Forgot to reload systemd (I'm still pretty new to this)
So, I did a:
root@truck # systemctl daemon-reload
root@truck # systemctl restart connman
and got PowerDNS working.
Thanks for all the help. ;-))
Oops! I can't reach my gateway anymore from my ReadyNAS...
Okay, I decided to revert to the old situation and remove PowerDNS, because, like I said, DNS is a core functionality to my environment. I figured it would be even better to have a Raspberry Pi doing DNS for me. So I bought one of those, configured it and it works like a charm! My ReadyNAS is using at as nameserver at the moment.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
