@Morris211 

 

DNS is a DHCP option, so it needs to be controlled by your DHCP server (which would typically be your ER605).

 

In Controller mode, there are override options, which would allow you to change the VLAN used by the SSID on that AP.  You could create multiple VLANs, each with their own IP subnet AND DNS SETTINGS, and then 'override' that VLAN on those APs where you want a custom DNS set.

 

 

Last though would be to use something like PiHole as your DHCP/DNS solution, you may be able to something there.

Correct, you are re-IP ing when you switch between customized sSSID (different VLAN) AP and the standard config APs. The only standard way to update a client's DNS setting is via DHCP, which would require that you renew your lease every time a roaming event happens. There's no standard way to retain seamless roaming AND have custom DNS setting on a per AP basis. You would literally need to build an external custom DNS proxy that queries the Omada system to determine which AP the client is currently attached to and then choose a DNS resolver IP based on that info. The delay added as a result would likely result in a negative client experience. Maybe there's a better way to solve this problem than with the path you have chosen? If only we knew what the problem was...

Let me know when you want to share the 'why' behind having some APs on DNS1 and others on DNS2.