@Ethan-TP,

I reproduced the problem.

It didn't work.

I tried another name and it also didn't work.

  @Ethan-TP

I deleted everything in LAN DNS.

I configured a new one now, but it's the same.

No responses and the same error.

In firmware version 2.31, it configured instantly. I could already ping. I'm doing everything right.

 

It took a VERY long time for this error to appear.

Oops.

I really don't want to roll back two firmwares.

  @Ethan-TP

Hey!

Thank you for your attention.

I only just understood now.

I have a few points to add and others as suggestions.

1- I understand there will be no more spaces. I found this bad, because programmatically in the product, in its code abstraction layer, you could have resolved to keep the field result with double quotes (""). Ex.: "VLAN 1 - MNGMT" and this would not affect the client. I would like to understand the reason for the change;
2- Understanding item 1 as something that will be like this from now on, I suggest that there be a way to critique the field. Including, even for others that we need to compose a name and identification. If it will be like this with this field, I consider that it is necessary to be a standard for everything and that Omada critiques the existence of unacceptable characters for the field;
3- I noticed that just changing the identification as you suggested doesn't work. I had to delete the records I had and recreate them from scratch. Thus, they became functional.

Thank you my friend, for your kindness and attention as always.
It's resolved here.

I would like feedback regarding what I suggested.

  @Ethan-TP.

I understand.
Thank you.

  @Ethan-TP

My dear sir,

Let me understand something, of course, if you can inform us.

Are you aware of which fields in the settings will follow these security changes? I consider what you are doing in this regard excellent and I want to get ahead of things so there are no more surprises.