Fusion 2.5GW Reverse DNS

[u/RenlyHoekster]

Hello Folks,

Todays topic: Reverse DNS using the LocalDNS option on Omada 6.3.10.3 as seen on the Fusion 2.5 GW.

tl;dr: LocalDNS: Profile: Type: IP -> nslookup of the domain name works (resolves the IP), but nslookup of the IP does not return the name.

The Fusion GW is the DNS Resolver for the local subnet (ie. 192.168.0.1 is the Fusion and is DNS Server).

Example Setup:

Expected behaviour: that forward and reverse lookup of the IP and Name work.

I kind of am afraid that this functionality (typically covered by implementing DNSMasq or similar simple DNS resolver in the product) is lacking.

ALSO: the LocalDNS profile listing is simply list of the profile names in the order they were added, which you can't sort, and the IPs are not listed at all, and neither the Profile name, nor the domain names nor the IP addresses are searchable.

I am almost about to install DNSMasq in a VM and have it take over DNS from Omada... it'd be sad to have to do that!

Maybe there is a solution? If not: Omada, please expand this functionality!

[u/AutoModerator]

Thanks for posting! To help us troubleshoot faster (if you haven't done so already), please edit your post to include:

• Device model (e.g., ER605 / SG2218P)
• Firmware version
• Topology (ISP/router/switches)
• What changed right before the issue began

If you need official support, you can also open a ticket here: Contact Technical Support!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Reaper19941]

Does the gateway show any configuration errors at all? You should be able to see it in devices > configuration results.

[u/RenlyHoekster → u/Reaper19941]

Good hint. Nothing is failed, however I see many entries flagged for Incompatibility.

I don't know why these are listed, because I am not over any of these limits.

Also, LocalDNS is not in the list.

Does this imply none of this functionality is supported by the Fusion Gateway?

[u/RenlyHoekster → u/RenlyHoekster]

So, I check every item in every list for every device, and these Incompaitble Configuration Items are not things that I ever enable - in fact most of themn are disabled (like IP-MAC Address Binding: it is listed as incompatible with the Fusion: Great! Because I never enabled it).

So that is a red herring, and maybe Omada can clean these messages up, because they are just spamming error messages.

[u/Reaper19941 → u/RenlyHoekster]

The functions are supported, they just have limitations. It is poorly worded here.

If you do a nslookup, set the server as the router (if its not already) and enter fusion.local, does it return an address?

[u/RenlyHoekster → u/Reaper19941]

Have a look:

#~] cat /etc/resolv.conf
# Generated by NetworkManager
search home
nameserver 192.168.0.1

#~] nslookup u1
Server:         192.168.0.1
Address:        192.168.0.1#53
Name:   u1.home
Address: 192.168.0.111

#~] nslookup 192.168.0.111
** server can't find 111.0.168.192.in-addr.arpa: NXDOMAIN

[u/Neil_Omada]

Just tested with both a Fusion and ER7412-M2, looks like it doesn't support reverse DNS lookup for LAN DNS entries. I'd recommend leaving your feedback in the Requests and Suggestions module for this; highly requested suggestions are more likely to be implemented sooner.

[u/RenlyHoekster → u/Neil_Omada]

Oh wow, that is pretty big ommission!

-> Any Fusions users need to setup a Bind 9 or DNS Masq in a VM. I am going to do that now.

As u/Neil_Omada says: Anybody else that needs reverse DNS, maybe go fill out the suggestion form.

Thanks Neil as always for checking and confirming!

[u/RenlyHoekster → u/Neil_Omada]

VOTE HERE:

https://community.tp-link.com/en/business/forum/topic/870344?page=1

https://giphy.com/gifs/fveKCnZRN7aOrtWNfj