You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AKS-Arc/aks-troubleshoot.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Troubleshoot common issues in AKS enabled by Azure Arc
3
3
description: Learn about common issues and workarounds in AKS enabled by Arc.
4
4
ms.topic: how-to
5
5
author: sethmanheim
6
-
ms.date: 04/01/2025
6
+
ms.date: 04/30/2025
7
7
ms.author: sethm
8
8
ms.lastreviewed: 04/01/2025
9
9
ms.reviewer: abha
@@ -25,24 +25,24 @@ The following sections describe known issues for AKS enabled by Azure Arc:
25
25
| AKS Arc CRUD operation | Issue | Fix status |
26
26
|------------------------|-------|------------|
27
27
| AKS cluster create |[Can't create AKS cluster or scale node pool because of issues with AKS Arc images](gallery-image-not-usable.md)| Partially fixed in 2503 release |
28
-
| AKS steady state | [AKS Arc telemetry pod consumes too much memory and CPU](telemetry-pod-resources.md) | Active
29
-
| AKS steady state | [Disk space exhaustion on control plane VMs due to accumulation of kube-apiserver audit logs](kube-apiserver-log-overflow.md) | Active
28
+
| AKS steady state |[AKS Arc telemetry pod consumes too much memory and CPU](telemetry-pod-resources.md)| Active|
29
+
| AKS steady state |[Disk space exhaustion on control plane VMs due to accumulation of kube-apiserver audit logs](kube-apiserver-log-overflow.md)| Active|
30
30
| AKS cluster delete |[Deleted AKS Arc cluster still visible on Azure portal](deleted-cluster-visible.md)| Active |
31
31
| AKS cluster delete |[Can't fully delete AKS Arc cluster with PodDisruptionBudget (PDB) resources](delete-cluster-pdb.md)| Fixed in 2503 release |
32
32
| Azure portal |[Can't see VM SKUs on Azure portal](check-vm-sku.md)| Fixed in 2411 release |
33
-
| MetalLB Arc extension |[Connectivity issues with MetalLB](load-balancer-issues.md)| Fixed in 2411 release |
34
-
33
+
| MetalLB Arc extension |[Connectivity issues with MetalLB](load-balancer-issues.md)| Fixed in 2411 release |
35
34
36
35
## Guides to diagnose and troubleshoot Kubernetes CRUD failures
title: Network validation error due to .local domain
3
+
description: Learn how to troubleshoot network validation errors due to the .local domain.
4
+
author: sethmanheim
5
+
ms.author: sethm
6
+
ms.topic: troubleshooting
7
+
ms.date: 04/30/2025
8
+
ms.reviewer: pradwivedi
9
+
ms.lastreviewed: 04/30/2025
10
+
11
+
---
12
+
13
+
# Troubleshoot network validation error due to .local domain
14
+
15
+
This article describes how to resolve the `Not able to connect to http://cloudagent.contoso.local:50000` error. This error occurs when you try to create and deploy an AKS on Azure Local cluster.
16
+
17
+
## Symptoms
18
+
19
+
You can deploy `.local` domains on Azure Local but might sometimes encounter failures during AKS scenarios, such as create, scale, update, upgrade, and delete. You might see the following error message:
20
+
21
+
`Error: Network validation failed during cluster creation. Detailed message: Not able to connect to http://cloudagent.contoso.local:50000. Error returned: action failed after 5 attempts: Get "http://cloudagent.contoso.local:50000": dial tcp: lookup http://cloudagent.contoso.local: Temporary failure in name resolution`
22
+
23
+
## Possible causes
24
+
25
+
There are two possible causes for this error:
26
+
27
+
1. Because `.local` is an officially reserved special-use domain name, host names with this top-level label are only resolvable via the multicast DNS name resolution protocol. Other mechanisms such as unicast DNS can also be used to resolve this name.
28
+
29
+
When a URL ending with `.local` for the failover cluster is used, a fully qualified domain name (FQDN) ending with `.local` is also used for the MOC cloud agent. The Azure Local 2503 release consists of various network validation tests. One of the tests tries to connect to the MOC cloud FQDN from the AKS Arc control plane VM. This specific test fails when the MOC cloud agent FQDN uses the `.local` domain name. This is because the **Go HTTP** client relies on standard DNS resolution, so it doesn't automatically resolve the `.local` address via mDNS.
30
+
31
+
1. When the on-premises directory is synchronized with Microsoft 365, you must have a verified domain in Microsoft Entra ID. Only the user principal names (UPNs) that are associated with the on-premises Active Directory Domain Services (AD DS) domain are synchronized. However, any UPN that contains a non-routable domain, such as `.local` (for example, `[email protected]`), is synchronized to an `.onmicrosoft.com` domain (for example, `[email protected]`). For more information, see [Prepare a nonroutable domain for directory synchronization](/microsoft-365/enterprise/prepare-a-non-routable-domain-for-directory-synchronization?view=o365-worldwide&preserve-view=true).
32
+
33
+
## Mitigation
34
+
35
+
If you are on Azure Local 2503 or a later release, don't use `.local` in the domain name.
36
+
37
+
Per the [possible cause #2](#possible-causes), if you currently use a `.local` domain for your user accounts in AD DS, we recommend that you change them to use a verified domain; for example, `[email protected]`, to properly synchronize with your Microsoft 365 domain.
38
+
39
+
As a temporary mitigation, the checks for the `.local` domain are disabled in the Azure Local 2504 release. For more information, see [What's new in Azure Local, version 2504](/azure/azure-local/whats-new?view=azloc-2504&preserve-view=true).
40
+
41
+
## Next steps
42
+
43
+
[Troubleshoot issues in AKS enabled by Azure Arc](aks-troubleshoot.md)
Copy file name to clipboardExpand all lines: azure-local/deploy/deployment-azure-resource-manager-template.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,6 @@ This article details how to use an Azure Resource Manager template in the Azure
22
22
## Prerequisites
23
23
24
24
- Completion of [Register your machines with Azure Arc and assign deployment permissions](./deployment-arc-register-server-permissions.md). Make sure that:
25
-
- All the mandatory extensions are installed successfully. The mandatory extensions include: **Azure Edge Lifecycle Manager**, **Azure Edge Device Management**, **Telemetry and Diagnostics**, and **Azure Edge Remote Support**.
26
25
- All machines are running the same version of OS.
27
26
- All the machines have the same network adapter configuration.
Copy file name to clipboardExpand all lines: azure-local/whats-new.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ ms.topic: overview
5
5
author: alkohli
6
6
ms.author: alkohli
7
7
ms.service: azure-local
8
-
ms.date: 04/29/2025
8
+
ms.date: 04/30/2025
9
9
---
10
10
11
11
# What's new in Azure Local?
@@ -20,7 +20,6 @@ This article lists the various features and improvements that are available in A
20
20
21
21
Starting with 2504 release, Microsoft introduced a new versioning schema. There are two 2504 releases for April. Here are the details of each release:
22
22
23
-
24
23
|Solution version |OS version |Deployment |
25
24
|---------|---------|---------|
26
25
|12.2504.1001.20 | 26100.3775 | New deployments only. |
@@ -32,7 +31,9 @@ For more information, see [Release information summary](./release-information-23
32
31
33
32
This release has the following features and improvements:
34
33
35
-
-**OS version changes**: Starting 2504, all new Azure Local deployments use a new operating system (OS) version **261000.3775**. Existing deployments continue to use the OS version **23598.1551**. For more information, see [Release information summary](./release-information-23h2.md).
34
+
-**OS version changes**:
35
+
- Starting 2504, all new Azure Local deployments use a new operating system (OS) version **261000.3775**. You can download the 2504 OS image from the Azure portal. You also need to get the driver compatible with Azure Local 12.2504 or Windows Server 2025. Existing deployments continue to use the OS version **23598.1551**. For more information, see [Release information summary](./release-information-23h2.md).
36
+
- If you've purchased Integrated System or Premier solution hardware from the [Azure Local Catalog](https://aka.ms/AzureStackHCICatalog) through your preferred Microsoft hardware partner, the OS should be preinstalled. Work with your Original Equipment Manufacturer (OEM) to get the OS image compatible with **12.2504** and driver compatible with Azure Local 12.2504 or Windows Server 2025.
36
37
37
38
-**.NET update installations improvements**:
38
39
- Increased reliability of .NET security update installations.
@@ -55,7 +56,7 @@ This release has the following features and improvements:
55
56
- Simplified the Azure portal experience for viewing the progress and history of update runs.
56
57
57
58
-**Add and repair node changes**:
58
-
- For Microsoft images, download the OS image matching the solution version of your existing cluster. See the [Release table](https://github.com/Azure-Samples/AzureLocal/blob/main/os-image/os-image-tracking-table.md) for the correct version. For OEM images, contact your Original Equipment Manufacturer (OEM).
59
+
- For Microsoft images, download the OS image matching the solution version of your existing cluster. See the [Release table](https://github.com/Azure-Samples/AzureLocal/blob/main/os-image/os-image-tracking-table.md) for the correct version. For OEM images, contact your OEM.
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments