@sReggy This phenomenon is so strange.
1. what is your network topology?
2. what is the IP of ER605 and the IP of PI?
3. what's your network configuration settings ?

@Yannie I've discovered the issue. To try to solve internal IP, i've set internal DNS on WAN interface ... so this was the root cause.

So may problem is ... how can I solve my internal IP displying on controller the assigned name (as configured in internal DNS)?

Thanks in advance for support.

Regards

Stefano

@sReggy I don’t think I fully understand what you mean, can you explain a little bit what “ how can I solve my internal IP displying on controller the assigned name (as configured in internal DNS) ” is ?

@Yannie I'll try to better explain what I want ...

I've an internal DHCP/DNS, running on a Raspberry PI using DNSMASQ. On DNSMASQ I've assigned fixed IP/hostname to relevant stations/iot devices.

If I display client list on OC200 controller or on ER605 gateway the client name is not the same that I've assigned in DNSMASQ, this because there is no reverse resolution of internal address.

The only configuration about DNS that I'm able to manage, is the one in ER605 related to WAN DNS, but if I configure the internal DNS on WAN interface the IP address of the DNS is banned from LAN interface, probably because it's considered as WAN IP.

The problem related to the ban is simply solved removing the IP address of the internal DNS from WAN configuration ... but the problem of reverse resolution of internal IP is already present.

Any idea on how to address it?

Thanks in advance

Regards

Stefano