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 (as well as reversed lookups) and forward other requests to my router.
Because name resolving is a very fundamental function, I want to reduce dependancies, so I figured it would be better to have pdns on my ReadyNAS.
I installed pnds-server and pdns-backend-mysql. Copied over the 'poweradmin' web-tree to have easy management, exported the MySQL database of the VM and imported it on the ReadyNAS.
So far, so good. The poweradmin web interface is working well, but I couldn't get pdns to start. I noticed 'bind' was running, so I killed that. ;-)
However, pdns still can't bind to port 53. Research learned me that 'connmand' is listening on that port.
Can I just disable it? The name "Connection Manager" seems to implicate that it's doing all kinds of stuff for the NAS, so I want to be carefull there.
What would be the right way to enable pdns on my NAS?
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. ;-))
5 Replies
Replies have been turned off for this discussion
Some extra information I forgot to give: I tried the app "DNS Server for ReadNAS" by ReadyNAS Guru. It didn't work, but I was unable to really uninstall it. Even after a reboot the app still appears in my list of apps. (Though icons were removed). Perhaps this is the problem
Update: I removed the directory /apps/dnsserver and the app is gone from my list of installed apps. pdns is obviously still unable to start due to the fact that connmand is still using port 53
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 connmanand got PowerDNS working.
Thanks for all the help. ;-))
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
