im setting up my new Route10, and when i setup the DNS server(s) under default vlan … its not being used by any devices connected. all devices connected show the ip of the router as the DNS. (i tried 9.9.9.9 or 1.1.1.1 or local ip – same issue)
I am doing something wrong, or is this a bug?
Thank you for the report! We’ve confirmed your issue, and we’ll provide a fix very soon.
This is resolved in the current cloud release, and will be resolved in the next Control software release as well.
something did change on the cloud controller, 'cuz now the devices get NO DNS ip at all. I power cycled the route10, and/or set the DNS in WAN and/or VLAN1 … devices get no DNS ip.
Side note: will be nice to have the option to reboot route10 from the controler. (I tried shift on each screen I can think of, but no luck)
OK, can you check it one more time? Sorry for the troubles.
DNS IP showing up now … and it’s working as intended.
if VLAN1 has blank DNS field, devices show route10 IP as DNS.
if VLAN1 has IP(s) listed, that shows up as DNS servers on the devices.
(domain name (on VLAN1) works now also).
I jut checked this after I rebooted everything, and my VLAN 99 is still using route10 for DNS, even though I have manual DNS entries.
I can see in the config on route10 that it is not being set for that VLAN.
I had to set it back to “default”, then set them again and it changed.
@Alta-Josh does it make sense that I had to undo the changes and make them again? That doesn’t seem good on a large network.
Yes, to me it makes sense to retain the known working configuration rather than to unexpectedly apply the configuration after a backend update. In this exact scenario I could understand why you would want the configuration to automatically apply, but I would still prefer to double check it and confirm it by hitting the Save button again.
I made another thread about this earlier today, but it would be great to be able to click “save” even when we haven’t made any new changes… to “force” a push out of what the current settings SHOULD be.
Agreed …. Maybe with the SHIFT trick/shortcut 
