DNS Node A Records
DOCUMENT CATEGORY: Runbook
SCOPE: DNS configuration for cluster nodes
PURPOSE: Pre-create A records for Azure Local nodes
MASTER REFERENCE: Microsoft Learn - Custom Active Directory configuration (required DNS records)
Status: Active
Overview
Pre-create forward lookup A records for each Azure Local node hostname before deployment. Whether you must also create the cluster name object (CNO) and virtual client access name (VCO) records depends on your DNS server, as described next.
What This Accomplishes
- DNS name resolution for cluster nodes
- Pre-staged DNS records for controlled environments
- Documentation of hostname to IP mappings
Which DNS records are required
Microsoft Learn 2610 (Custom Active Directory configuration) says: if your DNS server doesn't support secure dynamic updates, you must create the required DNS records before you deploy.
| Object | Record type | Required when |
|---|---|---|
| Machine name (every machine in the system) | Host A | DNS server does not support secure dynamic updates |
| Cluster CNO | Host A | DNS server does not support secure dynamic updates |
| Cluster VCO (the Cluster-Aware Updating client access point) | Host A | DNS server does not support secure dynamic updates |
Learn notes that Microsoft DNS servers integrated with Active Directory take advantage of secure dynamic updates. This runbook pre-creates the node records for controlled environments either way.
The active directory information in these documents should have been decided in the planning phase and discovery phases. These are just examples. Please update your scripts with the right OU information, right security groups, DNS, etc.
Prerequisites
- DNS Manager access or DNS Server tools
- Node hostnames and management IP addresses
- Authoritative DNS server permissions
Values from infrastructure.yml
The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.
DNS Record Creation
Pre-create forward lookup A records for each Azure Local node hostname. Create the cluster name (CNO) and virtual client access name (VCO) records now only if your DNS server does not support secure dynamic updates (see Non-dynamic DNS below). With secure dynamic updates available, those records are registered later by the cluster process.
- DNS Manager
- Orchestrated Script
- Open DNS Manager on an authoritative domain DNS server.
- Expand Forward Lookup Zones → select the Active Directory–integrated zone (for example,
improbability.cloud). - For each node:
- Right‑click the zone → New Host (A or AAAA).
- Enter node name (for example,
iic-azl-n01) and its management IPv4 address (nodes[].management.ip_address, for example192.0.2.11). - Leave "Create associated PTR record" unchecked unless the reverse zone is already delegated and managed.
- Click Add Host.
- Repeat for all node hostnames (example:
iic-azl-n01,iic-azl-n02,iic-azl-n03,iic-azl-n04). - Document the mapping (hostname ↔ IP) in the deployment artifacts and store in version control.
PowerShell
No script creates the records. The task folder holds only a placeholder. A placeholder prints
NOT IMPLEMENTED, changes nothing and exits with code 3. Create the records with the DNS Manager steps in the other tab, or with your own DNS process.
The earlier Set-DnsForwarding.ps1 is removed. It made conditional forwarders to 168.63.129.16, an address an on-premises DNS server cannot reach. Learn names host records for the machines, the cluster and its client access point instead.
The pre-cluster verification (Invoke-AzureLocalPreClusterVerification.ps1) checks the records before the deployment:
./Invoke-AzureLocalPreClusterVerification.ps1 -InfrastructureFile ./infrastructure.yml -Mode Verify
Verification
$ZoneName = (Get-ADDomain).DNSRoot
'hcinode01','hcinode02','hcinode03','hcinode04' | ForEach-Object { Resolve-DnsName "$_.${ZoneName}" -ErrorAction SilentlyContinue | Select Name,IPAddress }
Non-dynamic DNS: CNO and VCO records
Required only if your DNS server does not support secure dynamic updates (Learn 2610). Create a Host A record for the cluster CNO and one for the cluster VCO in addition to the node records. The names and IP addresses come from your deployment plan; the values below are placeholders.
#Requires -Version 7.0
Set-StrictMode -Version Latest
$ErrorActionPreference = 'Stop'
$ZoneName = 'contoso.com'
$ClusterName = 'clus01' # cluster CNO name from your plan
$ClusterIp = '10.0.0.20' # IP address allocated to the CNO in your IP plan
$CauVcoName = 'clus01-cau' # Cluster-Aware Updating client access point (VCO) name
$CauVcoIp = '10.0.0.21' # IP address allocated to the VCO in your IP plan
foreach ($rec in @(@{ Name = $ClusterName; Ip = $ClusterIp }, @{ Name = $CauVcoName; Ip = $CauVcoIp })) {
if (-not (Get-DnsServerResourceRecord -ZoneName $ZoneName -Name $rec.Name -RRType A -ErrorAction SilentlyContinue)) {
Add-DnsServerResourceRecordA -ZoneName $ZoneName -Name $rec.Name -IPv4Address $rec.Ip -CreatePtr:$false
}
}
Learn also notes for environments where secure dynamic updates are not possible that you must create the VCO manually (see Prestage cluster computer objects in Active Directory Domain Services), and that the Windows DNS client dynamic update setting is protected by drift control built into Network ATC. If you disable dynamic update (Get-NetAdapter "vManagement*" | Set-DnsClient -RegisterThisConnectionsAddress $false), create the VCO immediately afterwards to avoid the drift rollback. See Modify security defaults.
Disjoint namespace
A disjoint namespace exists when the primary DNS suffix of a domain member does not match the DNS name of its Active Directory domain (for example, a computer named with corp.contoso.com that is a member of na.corp.contoso.com). Before deploying, per Learn 2610:
- Append the DNS suffix to the management adapter of every node. The suffix must match the Active Directory domain name.
- Verify that you can resolve the hostname to the Active Directory FQDN.
# Append the DNS suffix (use the management adapter interface index on each node)
Set-DnsClient -InterfaceIndex 12 -ConnectionSpecificSuffix "na.corp.contoso.com"
# Verify resolution
nslookup node1.na.corp.contoso.com
You cannot use group policy to configure the DNS suffix list on an Azure Local instance.
Notes
- Node hostnames are always created in this task. Cluster CNO and VCO records are required now only when the DNS server does not support secure dynamic updates; otherwise they are registered dynamically.
- If secure dynamic updates are available and change control permits, the node-record step can be skipped; retain the section for controlled environments.
- Every machine that becomes part of the Azure Local system requires a DNS record.
- Verify a record with
nslookup <machine name>. - Reverse (PTR) records are optional; create only if the reverse zone is already in scope.
Validation Checklist
- DNS Manager or PowerShell access available
- Node hostnames and IPs documented
- A records created for all nodes
- Secure dynamic updates confirmed supported, or CNO and VCO Host A records created
- Disjoint namespace checked (DNS suffix appended on each node if it applies)
- Records resolve correctly
- Mappings documented in deployment artifacts
Next Steps
After configuring DNS records, proceed to Task 4 - Service & Admin Accounts for account creation.
Troubleshooting
Common Issues
DNS Record Creation Fails: Check DNS server permissions and zone access.
Records Not Resolving: Verify DNS server configuration and replication.
Dynamic Updates Blocked: Create the node, CNO and VCO Host A records manually (see Non-dynamic DNS above).
Support Resources
Alternatives
The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.
Navigation
| ← Task 02: Security Groups | ↑ Part 3: On-Premises Readiness | Task 04: Service & Admin Accounts → |
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-01-31 | Azure Local Cloud | Initial document |
| 1.1 | 2026-03-03 | Azure Local Cloud | Standardized runbook format |
| 1.2.0 | 2026-11-08 | Azure Local Cloud | Aligned to Microsoft Learn 2610: CNO and VCO records required when DNS lacks secure dynamic updates, disjoint namespace steps |