You are here

mesh host names not resolving?

5 posts / 0 new

Log in or register to post comments

Last post

Thu, 06/24/2021 - 12:55

#1

KM6SLF

KM6SLF's picture

mesh host names not resolving?

I'm able to access mesh services and nodes by IP address, but not by hostname (including localnode:8080).

I'm not sure where the problem is. My network topography is:

Cox cable modem to Ubiquiti DM
Ubiquiti DM connected by ethernet to Mikrotik hAP, which is connected to my various mesh service providing devices.

The PC I'm using is hard wired to the Ubiquiti DM and to a GL iNet AR150-EXT. Its settings are as follows:
"Wifi address": 10.5.140.14
LAN address: 10.44.96.113

WAN settings are:
Protocol: DHCP
DNS 1: 8.8.8.8
DNS 2: 8.8.4.4

If you're connected to the Southern California network you can probably access my hAP. It has the following settings:
"Wifi address": 10.51.179.148
LAN address: 10.59.57.65

WAN settings are:
Protocol: DHCP
DNS 1: 8.8.8.8
DNS 2: 8.8.4.4

The issue is the same on other computers on my network, so I think the issue might be a setting on the Ubiquiti DM... There are a ton of configuration options on this router, let me know what info you may need in order to help. Thanks in advance!

Thu, 06/24/2021 - 13:34

#2

K6CCC

K6CCC's picture

DNS issue

If your computer is trying to use Google DNS servers, they are not going to know anything about .local.mesh node names.

Thu, 06/24/2021 - 18:50

(Reply to #2) #3

KM6SLF

KM6SLF's picture

Should I set the computer DNS

Should I set the computer DNS server to one of the mesh nodes?

Thu, 06/24/2021 - 19:21

#4

K6CCC

K6CCC's picture

The computer is not going to

The computer is not going to be able to resolve mesh names unless it is getting DNS from the mesh (either directly or indirectly).

Fri, 06/25/2021 - 13:21

#5

KV3T

It sounds to me like your

It sounds to me like your Ubiquiti hardware that is between your mesh network and your computers is resolving DNS entries directly from the internet, not from the mesh network. You can check this by bypassing the Ubiquiti router, and plug a computer directly into the AREDN node. If it resolves mesh DNS there, then that confirms it.

Unfortunately I don't have a solution, but at least that can help identity the problem. Maybe someone more network savvy than I, or is familiar with the Ubiquiti DNS settings can provide a resolution. Setting static DNS entries in the router would work, but is more of a bandaid than an actual solution.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer