08-19-2022, 11:53 AM
moOde code doesn't tinker with how Linux DNS works it just sets up a few conf files based on the content of the Network Config screen.
Host name resolution works just fine on my network and there is no need to use the .local suffix. It's because the OS in the Router I use dynamically adds host names for LAN clients assigned a DHCP address to its DNS cache and its DNS functions as a forwarding (proxy) DNS.
I don't think all Router OS's implement dynamic DHCP updates to DNS and DNS proxy but instead rely on multicast DNS (host.local) to resolve LAN hosts and an external DNS for example 8.8.8.8 to resolve Internet hosts.
There also may have been some changes in linux client DNS caching as part of the 5.15 kernels.
Code:
# /var/www/inc/network.php
/etc/network/interfaces
/etc/dhcpcd.conf
/etc/wpa_supplicant/wpa_supplicant.conf
/etc/hostapd/hostapd.conf
# New for 8.2.0 to bridge Ethernet and WiFi (AP Router mode)
/etc/nftables.confHost name resolution works just fine on my network and there is no need to use the .local suffix. It's because the OS in the Router I use dynamically adds host names for LAN clients assigned a DHCP address to its DNS cache and its DNS functions as a forwarding (proxy) DNS.
I don't think all Router OS's implement dynamic DHCP updates to DNS and DNS proxy but instead rely on multicast DNS (host.local) to resolve LAN hosts and an external DNS for example 8.8.8.8 to resolve Internet hosts.
There also may have been some changes in linux client DNS caching as part of the 5.15 kernels.
