@Tournas

What do you mean?

I don't understand.

I'm using it with the Controller. Are you referring to removing it from Omada and making it work independently of the Controller, through its web interface?

No, and it doesn't make sense for me to test that. I work with the controller. It worked two versions prior. They need to review this, as it's certainly a bug.

  @Artur.Aragao 

You mentioned that the problem is with the er605 thats why I asked. By temporarily checking if lan dns works in standalone mode then you know the router works fine. You can then re adopt it.

  @Tournas

I will wait for the repair.

It's annoying, but not that much.

Thank you.

  @Artur.Aragao 

I can confirm that lan dns, nor dns override work on 2.3.3 in standalone.

I updated my routers (ER605) to ver. 2.3.3  (coming from 2.2.6).

I saw the function and was planning to use it with several routers that communicate to a hub location. What I noticed is that the lan dns would not work using the forward option, which seemed odd to me, since the router could ping the dns server via vpn.

I tried testing a simple forward to the internet and didn't work either.

Now, in my case, policy routing works, but haven't tested internet failover, I hope is not broken, but I suspect it is.

  @LinkDoogo 

I'll ask a friend here to look into it.

@Ethan-TP,

Can you help us with that?

Given that my original issue was resolved with a reset and set up of the whole environment from scratch I believe it was an update glitch in combination with a controller migration that happened at the same time. The thread can be closed.