@DanTheMan827 

 

I am sorry, but I don't fully understand what you are stating? Some examples and exact settings you made would help I guess?

 

DanTheMan827 wrote

First of all, the router is giving out the DNS that I set for the wan connection via DHCP to my devices, 

 

Although no router model was mentioned, I assume that on the router you didn't use your ISP's DNS's but maybe other Public ones, like CloudFlare or Google's? If you used one from say a device on your LAN that would be nice to know and how you did that (settings)?

 

DanTheMan827 wrote

when I use nslookup for known device host names it isn't using any sort of local DNS,

 

Again, not sure what you mean here? If on Windows, if you run this, what do you get"

 

===========

C:\>nslookup /?
Usage:
   nslookup [-opt ...]             # interactive mode using default server
   nslookup [-opt ...] - server    # interactive mode using 'server'
   nslookup [-opt ...] host        # just look up 'host' using default server
   nslookup [-opt ...] host server # just look up 'host' using 'server'

============

 

Do you mean for "KNOWN DEVICE HOST NAMES" the devices on your LAN?

 

DanTheMan827 wrote

and if I set the server to the local DNS of the router, it doesn't resolve any of the local device names via DNS.

 

Not sure what you mean, and where is this 'server'? Example please?

 

DanTheMan827 wrote

This seems like a bug more than anything, but not being able to use DNS names for computers and other devices does make things more difficult.

 

I'll assume you want to be able to address the LOCAL LAN devices by Device Name? The same names that are shown by the router GUI for what it has given DHCP IIP Addresses too? If so, I don't think ANY routers do that. That means if a device's name is "LAPTOP1" you can't do "NSLOOKUP LAPTOP1" which is I assume what you are stating?

 

Routers share device names via SMB, and many used SMB1, not the higher versions. MS has depricated SMB1 and if you hadn't enabled them manually, you can't even see the names.

 

That said, using NSLOOKUP isn't the way to see the network device shares, which is what I assume you want to do?

 

============

C:\>net view
Server Name            Remark

----------------------------------------------------------------
\\HP7855               Samba 3.0.37
\\IRV8700              Irv's 8700
\\TP-SHARE             samba server
The command completed successfully.

C:\>nslookup irv8700
Server:  one.one.one.one
Address:  2606:4700:4700::1111

*** one.one.one.one can't find irv8700: Non-existent domain

==================

 

I am using the ROUTER's DNS specifications which IS my ISP for IPv4 and v6

 

===============

Wireless LAN adapter Wi-Fi 2:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2603:9001:4801:d5c::1001
   Link-local IPv6 Address . . . . . : fe80::d0b:630b:7630:1b7f%16
   IPv4 Address. . . . . . . . . . . : 192.168.0.166
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : fe80::52d4:f7ff:fe68:3cc4%16
                                       192.168.0.1

=================

 

Again, if I read this wrong, I appologize. Still, real examples might help others too to see what you want to be able to do.

 

@IrvSp With other routers the name of the computer gets registered with the router so that when you run a command like "ping mydevice" from some other computer it would automatically find the IP of "mydevice", but with the Deco the computers don't even configure their DNS to the IP address of the main Deco running the DNS server, they configure to the WAN DNS configured in the Deco.

 

This isn't so much of an issue with computers running Windows because they advertise themselves on the network, but for devices that don't and only provide a hostname with the DHCP request, you have to use the IP address instead of the hostname.

 

If I use nslookup as follows, you can see it doesn't resolve

 

C:\Users\daniel>nslookup
Default Server:  dns.google
Address:  8.8.8.8

> ESP-E3FBF9
Server:  dns.google
Address:  8.8.8.8

*** dns.google can't find ESP-E3FBF9: Non-existent domain

 

However, DHCP sending the wrong DNS aside, on a router that properly registers DNS this should work, but it does not (this was run on a different network)
 

> server 192.168.1.1
Default Server:  [192.168.1.1]
Address:  192.168.1.1

> ESP-E3FBF9
Server:  [192.168.1.1]
Address:  192.168.1.1

Name:    ESP-E3FBF9.local
Address:  192.168.1.190

 

Simply running "nslookup ESP-E3FBF9" on any other router would return as follows

 

C:\Users\daniel>nslookup ESP-E3FBF9
Server:  MainRouter
Address:  192.168.1.1

Name:    ESP-E3FBF9.local
Address:  192.168.1.190

 

It's not an issue if the device advertises with mDNS or similar, but not all devices do.

 

I found this thread and it isn't just me https://community.tp-link.com/en/home/forum/topic/199010

 

This is a bug / flaw and should definitely be fixed in a software update to the router.

@DanTheMan827 

 

Ahh, some missing INFO, you are using Deco Mesh....

 

DanTheMan827 wrote

@IrvSp With other routers the name of the computer gets registered with the router so that when you run a command like "ping mydevice" from some other computer it would automatically find the IP of "mydevice", but with the Deco the computers don't even configure their DNS to the IP address of the main Deco running the DNS server, they configure to the WAN DNS configured in the Deco.

 

Yes, I can PING on an Archer A20 ('normal' router) my wife's computer (I have IPv6 on):

 

===============

C:\>ping l-xps8500

Pinging L-XPS8500 [fe80::a854:990b:4f72:5ec3%16] with 32 bytes of data:
Reply from fe80::a854:990b:4f72:5ec3%16: time=3ms
Reply from fe80::a854:990b:4f72:5ec3%16: time=3ms
Reply from fe80::a854:990b:4f72:5ec3%16: time=3ms
Reply from fe80::a854:990b:4f72:5ec3%16: time=4ms

Ping statistics for fe80::a854:990b:4f72:5ec3%16:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 4ms, Average = 3ms

================

 

However, NSLOOKUP still will not work...

 

==========================

C:\>nslookup
Default Server:  one.one.one.one
Address:  2606:4700:4700::1111

> l-xps8500
Server:  one.one.one.one
Address:  2606:4700:4700::1111

*** one.one.one.one can't find l-xps8500: Non-existent domain
> server 192.168.0.1
Default Server:  [192.168.0.1]
Address:  192.168.0.1

> l-xps8500
Server:  [192.168.0.1]
Address:  192.168.0.1

*** [192.168.0.1] can't find l-xps8500: Non-existent domain
> quit

C:\>nslookup l-xps8500
Server:  one.one.one.one
Address:  2606:4700:4700::1111

*** one.one.one.one can't find l-xps8500: Non-existent domain

C:\>

====================

 

Not sure NSLOOKUP why if you say it should it isn't? Even forcing it to use IPv4?

 

 

 

 

@IrvSp I've tried setting the DNS server nslookup uses by typing "server 10.0.0.1" into the interactive prompt and it changes the dns server that nslookup is using, but it still doesn't resolve any local DNS hostnames.

 

The issue is that the DNS on the router isn't acting as a DNS server, but rather a DNS forwarder, what it should do is run a DNS server that resolves hostnames that the router knows of on the local network and forward everything else out to the WAN DNS server.

 

As for you being able to ping other computers but not use nslookup, Windows includes various means to resolve other computers that are advertising themselves, they could be using mDNS, or NETBIOS, both of which completely bypass the router DNS server, but not all devices advertise using this protocol. @Tony 

@DanTheMan827 

 

Yes, most Windows PC's use NetBios. Net View (if SMB 1 is enabled) will show you those names.

 

By the way, routers get the name of the device other ways it seems. My A20 will show me names based on the MAC Address owner. I have to EDIT the names to something that means something to me.

 

My router is at 192.168.0.1, and that is the Server it uses.

 

Some people add a DNS Server to their LAN using a Rasberry Pi for instance. That would allow you to see the LAN devices by name I think?

 

See https://www.ionos.com/digitalguide/server/configuration/how-to-make-your-raspberry-pi-into-a-dns-server/ and it also has to be set to anything it can't resolve to go to a 'real' DNS, like a Public one or your ISP's.