Solved Remote Log to a local client, ip or hostname?

[mvadu]

I am trying to use one of my raspberry pi host as a remote log server. Raspberry is configured properly since I am getting many Tasmota switches logging there. In the beta5 ASUS Wireless Router RT-AC3100 - General Log section I tried adding the host name (fully qualified with .local) and I don't see the entries. Then I tried adding the same with ip adress and I can see the log entries. Is this by design or I am missing something?

I don't want to manually assign the IP if possible and drive most of my config using host names. I have a habit of changing the local IP pool ranges, and hard coded DHCP leases have caused problems in the past.

 

[mvadu]

Answering my own question probably, on the router's own scheme, I don't think it knows the client host names.

RT-AC3100 >ping raspberrypi4
ping: bad address 'raspberrypi4'
RT-AC3100 >ping raspberrypi4.local
ping: bad address 'raspberrypi4.local'
RT-AC3100 >ping 192.168.2.3
PING 192.168.2.3 (192.168.2.3): 56 data bytes
64 bytes from 192.168.2.3: seq=0 ttl=64 time=0.343 ms
64 bytes from 192.168.2.3: seq=1 ttl=64 time=0.275 ms
^C
--- 192.168.2.3 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.275/0.309/0.343 ms

 

[ColinTaylor]

This is expected behaviour.

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.

 

[mvadu]

Thank you @ColinTaylor , it does makes sense, and changing "Wan: Use local caching DNS server as system resolver (default: No)" to Yes worked with host names.

This is expected behaviour.

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.