Resolve IPs on active connections list

[txcanuck]

Hi,

I have enabled this setting (using the latest Merlin build) ... but it doesn't seem to turn IP addresses into hostnames for all IP's (using nslookup I assume?). Are others seeing this as well?

Thanks!

 

[RMerlin]

Hi,

I have enabled this setting (using the latest Merlin build) ... but it doesn't seem to turn IP addresses into hostnames for all IP's (using nslookup I assume?). Are others seeing this as well?

Thanks!

Not every IP has a reverse lookup entry in a nameserver.

 

[txcanuck]

Absolutely agreed! Only asking because some of the entries (that don't show a hostname) ... if I ssh in to the box, and do a "nslookup IP", I do in fact get a hostname.

But I may be missing the point ... .

Thanks!

 

[RMerlin]

Absolutely agreed! Only asking because some of the entries (that don't show a hostname) ... if I ssh in to the box, and do a "nslookup IP", I do in fact get a hostname.

But I may be missing the point ... .

Thanks!

Could also be that the authoritative nameserver for that IP is just too slow to answer. By the time you manually ran the nslookup over SSH, your ISP's DNS had already cached the delayed response.

 

[txcanuck]

Yep, that's possible. Is there a way I can check from the logs? Just trying to help out if I can - but if this is as expected no biggie at all.

Thanks!

 

[RMerlin]

Yep, that's possible. Is there a way I can check from the logs? Just trying to help out if I can - but if this is as expected no biggie at all.

Thanks!

No. It's all handled internally by the netstat-nat tool, it directly uses the Linux resolver.

 

[txcanuck]

Gotcha - NP. Is there a way to give this a bit more time? Asking because ~ half of the machines on my LAN show up, the other half don't.

Thanks for all your help!

 

[RMerlin]

Gotcha - NP. Is there a way to give this a bit more time? Asking because ~ half of the machines on my LAN show up, the other half don't.

Thanks for all your help!

Now that you mention those are internal LAN machines, that's a different story... In this case the (semi) authoritative nameserver is obviously your router's, and not some distant servers on the Internet that must be queried by your ISP's own DNS. So it has nothing to do with timing.

Chances are they aren't fully registered with your router's DNS, for instance because they are on a static IP, or they are using an older DHCP lease that predates the last router reboot.

 

[txcanuck]

Hi,

Sorry, not quite understanding the issue here (don't claim to be an expert on DNS, not even close ... ). If I run an nslookup on the router (ssh in to it), the result is what I'm after, so not sure what the DNS limitation may be. If nslookup works (IP address as argument), shouldn't the router be able to display the hostname?

Thanks!

 

[txcanuck]

Hi,

Just checking back in - as I upgraded to 380.57, and did a full factory reset + re-configured. I do like the way the wireless clients show up now (in AP mode) ... thanks! But still finding oddities in the name list. Any thoughts, or things I should try to change in the configuration?

Thanks again.