scotttiamit Posted December 21, 2017 Share Posted December 21, 2017 Hi guys, I have my unraid configured to use google for DNS but for some reason it instead keeps using DNS as it would be provided via DHCP? I have stopped the array and set it then started the array again, it stays the same, even a reboot did nothing. I have set it both through the GUI and manually in network.cfg file. I wasn't sure what DHCP_KEEPRESOLV meant exactly but have tried this as yes and no. I know the DNS is not working as it should because I can see in the firewall logs the DNS traffic from my unRAID using the wrong DNS server as you can see in the image below, the 52.32.39.15 address is the DNS server that would be provided via DHCP but that isn't enabled. Unraid version 6.3.5 Thanks. # Generated settings: IFNAME[0]="eth0" DESCRIPTION[0]="" USE_DHCP[0]="no" IPADDR[0]="192.168.0.100" NETMASK[0]="255.255.255.0" GATEWAY="192.168.0.5" DHCP_KEEPRESOLV="no" DNS_SERVER1="8.8.8.8" DNS_SERVER2="8.8.4.4" DNS_SERVER3="" MTU[0]="" SYSNICS="1" Quote Link to comment
Frank1940 Posted December 21, 2017 Share Posted December 21, 2017 I would suggest that you post up the server's diagnostics file. You can get it by entering diagnostics on the command line at the console. The file will be written in the logs folder/directory on your flash Drive. Quote Link to comment
s_mason16 Posted December 21, 2017 Share Posted December 21, 2017 im not saying this is the issue, but usually consumer routers have a dns function and if that is on, your unraid server could be trying to use that one rather than google's. I'd check your router and see if that is the case. and then if it is, you can just toggle it off. Quote Link to comment
scotttiamit Posted December 21, 2017 Author Share Posted December 21, 2017 Thanks mate but I cannot turn the DNS off on the firewall as this needs to be used by other devices as we use a DNS filtering service. Just need unRAID to use what is set. I will try dumping the diagnostics info... Quote Link to comment
scotttiamit Posted December 21, 2017 Author Share Posted December 21, 2017 kotik-diagnostics-20171222-1138.zip Diagnostics attached. Quote Link to comment
scotttiamit Posted January 8, 2018 Author Share Posted January 8, 2018 Any ideas anyone? This is still not working as intended? Quote Link to comment
bonienl Posted January 8, 2018 Share Posted January 8, 2018 What is the output of cat /etc/resolv.conf Quote Link to comment
scotttiamit Posted January 8, 2018 Author Share Posted January 8, 2018 Hi, result is 52.32.39.15 which should be 8.8.8.8 and 8.8.4.4 as set in the settings. Quote Link to comment
scotttiamit Posted January 8, 2018 Author Share Posted January 8, 2018 I did a 'nano /etc/resolv.conf' and updated the file and saved the changes. I presume this will work for now, not sure if it will stick after a reboot or not but there must be a bug around the GUI settings not being applied correctly. Quote Link to comment
bonienl Posted January 8, 2018 Share Posted January 8, 2018 It should work properly, but change this in the network.cfg file DHCP_KEEPRESOLV="yes" Quote Link to comment
scotttiamit Posted January 8, 2018 Author Share Posted January 8, 2018 OK thanks. Done. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.