Cannot turn off DNS Server - Amahi 7.1 (Fedora 19)
System 3.10.5-201.fc19.x86_64 ,x86_64
Today I tried to turn off the DNS Server permanently.
I followed the Instruction from here:
But everytime I reboot the system, the DNS Server is running again.
#1 Updated by bigfoot65 almost 8 years ago
- Status changed from New to Feedback
- Assignee changed from bigfoot65 to doaserver
Not sure it can be easily turned off. The guidance you referenced I do not believe is specific to Fedora 19. Will have to do some research to find out why it does not turn off. My guess would be that Monit is restarting it or it's set to start on boot.
Is there a reason you want it off? Without the DNS server on the HDA, it will not properly resolve URLs for apps.
If you don't want to use the HDA DNS for your client, then point the client to a different DNS server. I believe you can also change the DNS provider in Amahi 7 as well, if you prefer a different one than OpenDNS.
#2 Updated by doaserver almost 8 years ago
I installed the system as a DLNA Server and network drive. I don't want to use other apps.
The Server will only run if he's needed. The rest of the time he is waiting for magic packets to wake up (WOL).
The moment I shutdown the system the router don't recognize that there is no DNS server in the local network anymore and therefore the router don't take over hda's job. You can imagine the nasty result...
When I point the clients to a different DNS server I have to configure this in the DHCP Server or have to use static IP, am I right?
#3 Updated by bigfoot65 almost 8 years ago
If that is the case, then why not use DHCP and DNS from your router? Then turn off DHCP on HDA and leave DNS alone. As long as router is handling DHCP and DNS, it will not see the HDA DNS.
You should be able to access shares and DLNA via IP address. That should eliminate your problem.
#8 Updated by bigfoot65 almost 8 years ago
There is no issue here. The Settings option in the Networks tab allows disabling of the DNS. The Servers tab shows it as running, but that is due to it sharing the same service as DHCP.
This is not really a bug, but by design. Closing as no further action required.
Also available in: Atom