Hub Two not resolving local host names

[#1]

---

@pvmb wrote:

...What steps did you take to direct all your computers at the Hub Two for DNS?

TIA

:

On my Win8 notebook with the Technicolor TG582n router I used to be able to ping the router by name as 'router' (or 'dsldevice.lan' - the latter seemingly something to do with the OS or router) whereas now I seem only to be able to ping the router by IP address. It's hosts file is the default with no entries added by me. (So how did it do it?)

I pointed the resolver config file on the local host machines to 192.168.1.254 (IP address of the Hub 2). I depends on your OS on how the resolver is configured. On my Mac I use the Settings menu and on the Raspberry Pi's I edited /etc/resolv.conf. (I somehow had these all pointing to an external DNS server?) Once I directed all my local hosts to use the Hub 2 as their DNS server then local hostname lookups worked. 

However, I don't know the host name of the actual Hub 2 router, as I never need to access it by hostname. It may have one, but I am not familiar with how to find out if it does or doesn't.

[#2]

If you tracert the router's IP address result should show device 'name'.

[#3]

Don’t think my suggestion wii work as l’ve just found an entry in my host file.

Will look tomorrow to see if there’s another way…. 

[#4]

Just to confirm. Back on TG582n router at the moment.

ping router --> router.lan [192.128.1.254]
ping dsldevice --> dsldevice.lan [192.128.1.254]

In fact, unlike the OP, I can ping by name hosts on the lan identified by the Hub Two. But, so far the Hub itself has not declared itself by name so can only ping its IP address directly.

[#5]

Did you try a tracert as suggested by @Champnet?

I did on my Asus router and it returned a pingable name.

PS C:\Users\ian> tracert 192.168.1.254

Tracing route to DSL-AC88U-4DB0 [192.168.1.254]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  DSL-AC88U-4DB0 [192.168.1.254]

Trace complete.
PS C:\Users\ian> ping DSL-AC88U-4DB0

Pinging DSL-AC88U-4DB0 [192.168.1.254] with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.254:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS C:\Users\ian>

[#6]

Well, waddya know? The Plusnet Hub Two router is called.....

PLUSNETHUBTWO 🤣

tracert 192.168.1.254

Tracing route to PLUSNETHUBTWO [192.168.1.254]

ping plusnethubtwo

Pinging plusnethubtwo [192.168.1.254]

Pity they couldn't have just named it the shorter HUB2!

-----

PS. Success! It has another, shorter name. 😁

ping hub

Pinging hub.home [192.168.1.254]

So "hub" it is then. Great.

[#7]

From my iMac

$ ping plusnethubtwo

ping: cannot resolve plusnethubtwo: Unknown host

 $ ping hub

ping: cannot resolve hub: Unknown host

You sure your local hosts file doesn't have these names defined?

[#8]

@ksaro1 what do you get from tracert 192.168.1.254?

[#9]

---

@Browni wrote:
@ksaro1 what do you get from tracert 192.168.1.254?

---

I'll have to get back to you on that. I don't have any Windows machines available atm. I mainly use Mac. iPad, rpi and Android devices on my home network. My wife has a PC, which I'll have to get and run tracert on.