Internal DNS resolution
Internal DNS resolution
Hi,
Hopefully an easy question to resolve.
Recently replaced my BT Router provided wifi and Powerline extenders with a 3 unit Deco M9 setup.
I have the wifi on the BT router turned off, using only the deco's for wifi. The BT hub knows nothing about what is connected to the deco's (as far as i can tell)
In my previous setup, i could resolve internal hostnames in DNS, simply by typing the hostname without any domain, i.e "ping nas". I presume the BT hub was registering them into an internal DNS domain for me.
Now i have the deco's installed DNS resolution does not work. Netbios/SMB seems to still work, i,e on a windows laptop i can browse the networks and see devices, but from a linux/mac command line i can not resolve any names to IP addressess, meaning i have to fire up the deco app to find out the IP's
I'm pretty sure this isn't how it is supposed to be and am missing some obvious config step or don't have a default domain set on my linux machine(s)
Any advice?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@dantana The best way, if we use Deco M9 as router, we need router features. Otherwise it is not useable.
In my case, Deco M9 are in bridge mode and a PfSense is the router. I didn't plan that, but nom it is like that...
- Copy Link
- Report Inappropriate Content
man, here I was thinking my whole network somehow became misconfigured.
tplink please add local hostname resolution!
so frustrating.
- Copy Link
- Report Inappropriate Content
So much for a router...
- Copy Link
- Report Inappropriate Content
I just ran into this same issue on my x60, devices that advertise themselves with mDNS can be used by hostname, but that isn't the router resolving the hostname so you can't use something like nslookup and anything that doesn't know about mDNS (like an older device) won't resolve by hostname.
It's not a huge issue since most of the devices I would connect to / from do support mDNS, but a lot of smart devices don't even advertise themselves with anything besides registering with the local DNS, so I have a lot of unnecessaryIP reservations set up and have to remember which device has which IP.
This is a fairly major feature to be missing from a router as expensive as this though, every previous router I've owned has resolved local DNS hostnames and had a web interface for configuration instead of requiring an app.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I am assuming this is only the problem when Deco mesh runs in Router mode. For Deco in Access Point mode it would not be an issue.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
You can put me down for wanting this too. Some old devices on my network incorrectly expect that gateway can resolve dns requests. What makes the lack of this feature even worse is that you can't turn DHCP off on Decos. So, I can't add my own DHCP server (like a pi-hole) to resolve local dns requests. One hack I've been using is append ".local" to hostnames. I believe that uses Netbios to resolve the name instead of DNS. I think this is the first router I've ever seen that doesn't support local dns caching.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Short update to this thread, seeing as I raised the issue originally. The quick response is this is now working, and my problem has been solved. I don't understand how.
The longer answer is that I recently "upgraded" my mesh network to another manufacturer as my family were complaining of a dead spot on the top floor of the house and I didn't want to buy another Deco unit because of this issue, so though it time to upgrade.
The new system was terrible. I won't name and shame them, but I was seeing huge packet loss on the network and devices would loose connectivity for minutes at a time.
After a week of living with this (and i bought extra units incase it was a coverage issue (it wasn't, or at least the extra units made no difference) pressure from my family made me re-instate the Deco M9's, which had been factory reset ready for selling on eBay.
This evening out of interest, i tried to see if i could resolve local DNS names. They don't work unqualified, as they did with the BT Hub direct, but they work perfectly on the .local subdmain, i.e raspberrypi.local or nas.local both at the linux command line and in a browser.
I beginning to wonder if this was ever a problem - i can't recall exactly hiw much troubleshooting I did when i first got the units, but TP link support and other owners also posted saying internal DNS resolution was not supported.
As of today (30 October 2021) i can confirm local (internal) DNS resolution does work if you suffix the .local domain to the name (or add it to your resolve.conf)
I shall be buying an additional M9 unit in the next few days
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 24267
Replies: 20