The server did not want to forward “*.local” DNS queries
You have a DNS server that is the master of the ".local" domain, and your Artica server won't forward requests and returns the error "Non-existent domain".
The
.localdomain is typically reserved for Multicast DNS (mDNS) to facilitate the automatic discovery and resolution of hostnames on local networks without the need for a central DNS server.
This feature is available on Artica 4.50 Service Pack 1 or Artica 4.50 Hotfix 20240524-16
Why .local domain is reserved ?
Zero-Configuration Networking:
- mDNS, as part of Zero-Configuration Networking (ZeroConf), allows devices to automatically discover each other on a local network without manual configuration or the need for a central DNS server.
- By reserving
.local, devices can use familiar hostname-based addressing within a local network, simplifying network setup and management.
Service Discovery:
- Along with DNS Service Discovery (DNS-SD), mDNS facilitates the discovery of services such as printers, file shares, and other network services advertised by devices on the local network.
- Devices can query for services (e.g.,
._http._tcp.local) and receive responses about available services and their corresponding addresses.
Avoidance of Global DNS Conflicts:
- Reserving
.localfor mDNS ensures that names used within the local network do not conflict with names in the global DNS namespace. - This reservation prevents potential issues where a
.localdomain might be inadvertently queried on the global internet, leading to ambiguity or misrouting.
How to bypass and force ?
If you've used the .local domain for your own local network and would like the DNS service to forward queries to your DNS server, here's the procedure.
- On the main configuration select the link “
Disable ”local" Reservation" - Turn to on this option and click on Apply
