Title: Add Support for old-styled .local Domains...
Description: Since forcing the normal behavior to ignore .local domain names for mDNS. It can be a charm to build in a switch to override this from out of the box. or by detecting the servers domain name to enforce the use of the "domains-DNS".
Actually it happens only on the control-plane nodes, they are trying to connect to the Cluster / ResourceBridge over the local clustername, ending with the famous .local TLD for example myDomain.local --> myCluster.myDomain.local.
to prevent connection or resolution issues we must set manually on each control-plane node
/etc/systemd/resolved.conf
DNS=<IP1> <IP2>
DOMAIN=~local
after this the dns resolutions is working like expected.
Yes i know that .local TLD is quite old, but in some environments we can't change it in the future.
but if we're able to use a build in mechanism to prevent this, so AzureLocal can be more versatile for more customer-environments
Title: Add Support for old-styled .local Domains...
Description: Since forcing the normal behavior to ignore .local domain names for mDNS. It can be a charm to build in a switch to override this from out of the box. or by detecting the servers domain name to enforce the use of the "domains-DNS".
Actually it happens only on the control-plane nodes, they are trying to connect to the Cluster / ResourceBridge over the local clustername, ending with the famous .local TLD for example myDomain.local --> myCluster.myDomain.local.
to prevent connection or resolution issues we must set manually on each control-plane node
/etc/systemd/resolved.conf
DNS=
<IP1><IP2>DOMAIN=~local
after this the dns resolutions is working like expected.
Yes i know that .local TLD is quite old, but in some environments we can't change it in the future.
but if we're able to use a build in mechanism to prevent this, so AzureLocal can be more versatile for more customer-environments