Can't access device on LAN by hostname

[ColinTaylor]

Also no default gateway

That's also correct. Leaving those fields blank means that the router gives out it's own IP for those things. If you hover your mouse over the field names you should see a pop-up help message.

 

[den75]

Thanks for all the help so far. It's not a huge burden since I can still get to it with the IP and I can always place that in my local hosts file. Only thing is if/when that changes and it gets assigned a new IP I'll have to change that.

 

[ColinTaylor]

No, I don't. It's not even enabled

Thanks for all the help so far. It's not a huge burden since I can still get to it with the IP and I can always place that in my local hosts file. Only thing is if/when that changes and it gets assigned a new IP I'll have to change that.

You could 1) enable the manual assignment and then 2) create an entry for it in the "Manually Assigned IP around the DHCP list". That way it would always have the same IP address.

 

[den75]

You could 1) enable the manual assignment and then 2) create an entry for it in the "Manually Assigned IP around the DHCP list". That way it would always have the same IP address.

Thanks, I'll have to give that a shot

 

[L&LD]

You can type it in manually and reboot both the router and the apex.

 

[den75]

You can type it in manually and reboot both the router and the apex.

Thanks, didn't realize I could do that

 

[Marko Polo]

Wanna up the thread. I have the same problem but unlike the OP, I have both Ethernet and WiFi MACs added to the DHCP static list.
However, connect to RDP via hostname works only for Ethernet, but no WiFi. More odd, nslookup gives following

C:\Users\user>nslookup cubical
Server:  router.asus.com
Address:  192.168.1.1
*** router.asus.com can't find dev-wifi: Non-existent domain

while connected either Ethernet or WiFi. At the same time, Ethernet RDP works.
Any suggestions?

 

[Marko Polo]

And yes, I see in log

Apr 12 14:55:59 dnsmasq-dhcp[283]: DHCPREQUEST(br0) 192.168.1.100 XX:XX:XX:XX:XX:XX
Apr 12 14:55:59 dnsmasq-dhcp[283]: DHCPACK(br0) 192.168.1.100 XX:XX:XX:XX:XX:XX device-wifi

for BOTH adapters.

 

[Marko Polo]

Nobody have faced this? Is it Windows DHCP problem or router one?

 

[john9527]

Make sure you assigned your lan a domain name at the top of the LAN>DHCP Server page
If you need a suggestion
home.lan
is a safe choice.

 

[OnlyMostlyDead]

Make sure you assigned your lan a domain name at the top of the LAN>DHCP Server page
If you need a suggestion
home.lan
is a safe choice.

This was the cause of my particular issue. Once I entered the domain name, my router rebooted myself, and when it came back, I could access all members by <hostname>.<lan-domain-name>. Thanks!

 

[yoggit]

I have this problem too. Adding a domain didn't address it!

I'm running 384.12 on RT-AC86U:

As you can see, the local DNS query works:

admin@RT-AC86U:/tmp/home/root# dig @localhost megs-phone

; <<>> DiG 9.14.4 <<>> @localhost megs-phone
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11510
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;megs-phone. IN A

;; ANSWER SECTION:
megs-phone. 0 IN A 192.168.50.161

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Dec 31 14:53:52 AEDT 2019
;; MSG SIZE rcvd: 55

but a ping doesn't resolve.

admin@RT-AC86U:/tmp/home/root# ping megs-phone
ping: bad address 'megs-phone'
admin@RT-AC86U:/tmp/home/root#

other hosts on the LAN have no problems with hostnames, just the router. I have no DNS servers specified, no WINS server... all very standard.

Interestingly, my arp cache only has a hostname for my ISP, and nothing local!


Any ideas?

Thanks,
Jon

 

[ColinTaylor]

@yoggit There was a change of behaviour in 384.12. By default the router no longer uses the local DNS server to resolve addresses but goes directly to the WAN servers. You can change back to the old behaviour at Tools -> Other Settings.

384.12 (22-June-2019)

  - CHANGED: The router will now use ISP-provided resolvers
             instead of local dnsmasq when attempting to
             resolve addresses, for improved reliability.
             This reproduces how stock firmware behaves.
             This only affects name resolution done
             by the router itself, not by the LAN clients.
             The behaviour can still be changed on the
             Tools -> Other Settings page.

 

[yoggit]

Champion Colin. Thanks mate.