DNS servers in Azure Local Logical Network can't be changed

Open

#175 opened on Sep 23, 2025 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 28/100

Issue type: Feature
Clarity: Needs clarification
Activity status: Stale
Tech stack: azure
Domain: cloud, networking

Research direction

Start by reproducing the inability to edit DNS servers in an Azure Local Logical Network and compare the current behavior with the previously available option. Confirm the expected DNS-change workflow for migrating Active Directory servers and removing the old subnet; done means the DNS servers can be modified and the migration scenario is supported.

Written by the indexing model from the issue text.

Description

In the near future, we want to migrate the Active Directory servers and remove the old subnet. However, we are unable to modify the DNS servers in the Azure Local Logical Networks. It appears that this was possible before. Can this option be added again?

Dominant language: PowerShell
Stars: 78
Forks: 60
Avg merge: 1d 6h
Merged PRs (30d): 5

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

More from Azure/AzureLocal-Supportability

docs: Clarify DCBX requirement vs DCBX willing mode in TOR QoS reference Open

Difficulty 1/5 1-3 hours Newbie friendliness 88/100

Azure/AzureLocal-Supportability#290 · Opened May 22, 2026
docs: Clarify DCBX requirement vs DCBX willing mode in TOR QoS reference Open

Difficulty 1/5 Under an hour Newbie friendliness 82/100

Azure/AzureLocal-Supportability#289 · Opened May 22, 2026
Solution update fails at UpdateSecuredCore (ConfigureSystemGuardLaunch 2≠1, 0x82d0000c) - orphaned ApplyAndAutoCorrect machine configuration assignment enforcing DRTM=disabled on one node Open

Difficulty 5/5 Over a week Newbie friendliness 35/100

Azure/AzureLocal-Supportability#328 · Opened Jul 11, 2026
Readiness Check Fails if certain PSGallery Powershell Modules are installed Open

Difficulty 4/5 3-5 days Newbie friendliness 45/100

Azure/AzureLocal-Supportability#272 · Opened Apr 10, 2026
Bug: Data loss if CSV created on node added to cluster, then node evicted later. Open

Difficulty 5/5 Over a week Newbie friendliness 25/100

Azure/AzureLocal-Supportability#253 · 1 comment · Opened Feb 23, 2026

All issues in Azure/AzureLocal-Supportability

Similar issues

[BUG] GkeTpuCluster queries metadata.google.internal for MEGASCALE_SLICE_ID even when TPU_SKIP_MDS_QUERY is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

jax-ml/jax#40854 · Opened Sep 22, 2026
fix(mcp): `permanently_delete_cloud_{source,destination,connection}` lack `workspace_id` param, unusable without a default workspace Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

airbytehq/PyAirbyte#1201 · Opened Sep 21, 2026
[BUG] Route53Resolver: CreateResolverEndpoint requires IpAddressRequests, but the AWS member is IpAddresses, so no SDK client can call it Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

floci-io/floci#4108 · Opened Sep 21, 2026
wm_gcp_parse_output underflows its heap buffer by one byte Open

level/task module/gcp type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

wazuh/wazuh#39525 · Opened Sep 21, 2026
[Bug]: aws_lb_listener silently ignores tcp_idle_timeout_seconds on TCP_UDP listeners Open

bug needs-triage service/elbv2

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

hashicorp/terraform-provider-aws#50100 · 1 comment · Opened Sep 21, 2026

More Cloud issues

A short digest of beginner-friendly GitHub issues.