@avargas 

avargas wrote

  @hammer86 Any news about this know  issue , any alternative different to install a local DNS server?  thanks

 

The last post from Fae was this

 

"At this time, we do not have specific information on when the feature will be released or which router model will add the feature of local DNS server finally. "

 

In other words: "don't count on it".

 

@hammer86 Yes, but this not an acceptable answer. It's a slap in the face.

 

@Fae When will this feature be finally ready?

Would complete the Omada solution for me

Even basic functionality would be greatly appreciated

It will be better if this feature can be implemented in the OC200/OC300 SDN cores.

Maybe a simple solution here would help most people.

 

At least for me I don't need all the IP address in my environment to be able to be DNS resolved. I have a couple of servers, NAS, etc. which I prefer to access via hostnames instead of IP addresses (easy to remeber and easy to administrate based on changes).

 

I have looked at another SDN provider and they do this in a very simple way:

 

Their controller allows in DHCP settings to set a fixed IP for devices. Once you set a fixed IP you have the option to give this host a hostname. Once you do this there is a simple entry in the dnsmasq config file:

 

host-record=router.localdomain,router,192.168.1.1

 

That's it, with this simple config dnsmasq can resolve local hostname to IP addresses for devices with a fixed IP adress.

 

I believe ER605/Omada is using dnsmasq as well so this should be fairly easy to implement.

Mandatory for IPv6

  @aschmid thanks for this quick solution , justo to understand    the dnsmasq contig  file is  in to ER605 controller or  in other host , if so , how can acces to this file in to controller

thanks

 

 

avargas wrote

  @aschmid thanks for this quick solution , justo to understand    the dnsmasq contig  file is  in to ER605 controller or  in other host , if so , how can acces to this file in to controller

thanks

 

 

  @avargas this is not something a user can do but TP-Link must implement. As I said in my post another SDN vendor is doing it this way ... might be slightly different how TP-Link can do it. This was just for example. TP-Link must act here.