Not sure why ASUS decide to have
.local suffixes defined in hosts in first place.
I am tempted to remove from my
unbound.conf as it is a bit inconstant.
But maybe it will have side effects as router.asus.com in Mesh etc.
This will behave consistently when executed from my router and Windows command line
Code:
ping -4 myrouter.mydomain
ping -6 myrouter.mydomain
ping -4 myrouter.local
ping -6 myrouter.local
ping -4 myrouter.
ping -6 myrouter.
But guess what happens if do instead
Code:
ping -4 myprinter.mydomain
ping -6 myprinter.mydomain
ping -4 myprinter.local
ping -6 myprinter.local
ping -4 myprinter.
ping -6 myprinter.
Well on my Windows workstation on the LAN all of them work perfectly.
So it must be bypassing my router's
unbound - need to double check network traffic.
While on router, only the first cmd works because
unbound_manager converting hosts.dnsmasq only created just myprinter.mydomain IPv4 entry. Pretty sure dnsmasq was able to cope with skipped domain and generate IPv6 response too (not sure what issues prevent DNS64 from unbound.conf - read threads, but no real evidence).
EDIT:
Tested the latter section on with dnsmasq enabled and the extra one that works on the router is
ping -4 myprinter. Not sure why with
unbound takign care of DNS it does not.
PS. Why do not we have Merlin IPv6 thread (we have one for static IPv6)?