Hello !

Thanks for your answer, nevertheless, not relevant.

for External domain, it doesn't apply, as external, standard resolution applies.

Now for Internal, you may have several local network ( one for LAN, one for WIFI ), so, the mDNS doesn't work.

Workaround is to switch the Wifi access point ( so the deco itself ) as bridge, relying on another DHCP server to provide all standard attributes. You generally don't want that as you are loosing almost all feature from the deco.

All that to say that I'm surprised that a basic and standard ( ref :   ) is not implemented in Deco.

AS it doesn't require any hardware modification but just software update ,

Is there a way to set this feature for the next updates ?

Thanks

 agreed.. whatever their DHCP implementation, the ability is there at the software level... simply adding the field to allow us to set a custom domain shouldn't be hard. and for support to come back and say "just use local" - No.. this RFC explains that "home arpa" is correct, not local, so there should be a choice.

rfc8375 (can't link, just search for it)

I run a lot of server software at home, and having FQDN is essential.

if a $50 router has it, why does a "premium" product not offer the option.