You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
-
It is, but adding name-servers there didn't work, neither did having the router pick up the DNS servers from my ISP
I did find a fix / workaround - and learned a bit more about the router - using dnsmasq
- added 127.0.0.1 as the global name-server (via the gui), then
- via the cli, set some forwarding name-servers (to opendns for the moment),
- disabled name-server updates from the isp (connected via dhcp on eth1), and
- had dns requests on all other ports (eth0, 2, 3, 4 & switch0) set to listen. finally
- set dns forwarding to system
tl;dr I fluked a fix
- added 127.0.0.1 as the global name-server (via the gui), then
I have an EdgeMax @velocio question
A power outage yesterday played havoc with my network - my wireless APs stopped behaving (suffering interference, limited signal and becoming isolated from the network), and DNS lookups stopped entirely.
Factory resetting the EdgeMax, and upgrading AP firmware fixed the connectivity, but the DNS is still shot (it took me a while to realise this, as most external connections are via an ssh tunnel)
I can't find any GUI screen to set DNS, but I did find a command that I could enter over via ssh
> set service dns forwarding name-server 8.8.8.8
But this doesn't work, and DNS is still borked
Do you have any ideas?