DNS SERVFAIL and Non-existent domain Issue for New Records in domain.local Zone

Question

We are experiencing an issue with our internal DNS server related to the domain.local zone. Here are the details:

Issue Description:

• Existing DNS records (e.g., srvvmdc01.domain.local) resolve correctly and return the expected IP addresses.
• When we add a new DNS record (e.g., test.domain.local), nslookup returns:

*** Server failed

*** Non-existent domain

• This occurs on both internal DNS servers.

Observations:

• Only new records fail to resolve; old records continue to work.

Thank you for your support.

Answer 1

Hey @Sardor Suvonov,

It looks like you’re facing a DNS resolution issue with new records in your domain.local zone. Since your existing records resolve correctly, the problem could likely be tied to how the new records are configured or a delegation issue.

Before proceeding, could you please confirm whether your domain.local zone is hosted on Azure Private DNS or on an on‑premises Windows DNS server?

Here are a few things you can check:

1. Verify DNS Record Configuration: Ensure that the new DNS record (e.g., test.domain.local) is set up correctly in the DNS management interface. Double-check the name, type, and any associated data (like the IP address).
2. Propagation Time: If you just created the record, remember that DNS changes can take some time to propagate. Depending on your server's TTL (Time to Live) settings, this could affect how quickly the new records are visible.
3. Check for Zone Delegation: If your domain.local zone is delegated improperly, it might not resolve correctly. You can verify the NS records and ensure they point correctly to your DNS servers. For that, you can use nslookup -type=NS domain.local
4. Check DNS Cache: On your DNS server, ensure that the cache is cleared to find the new records afresh.
5. Look for Errors in DNS Server Logs: Check the logs on your internal DNS servers for any errors or warnings that may give you more insight into what's happening.

If none of these steps resolves the issue, please provide the below information.

1. When was the new DNS record created? Have you allowed adequate time for propagation?
2. Are there any specific error messages or logs from your DNS server that could provide more context?
3. Are there any DNS servers between the client and your internal server that could be caching old data?
4. Can you confirm the type of DNS records you are creating (A, CNAME, etc.)?

Hope this helps you get started on resolving the issue! If you need more assistance, feel free to share additional details!

Refer:

• Troubleshoot Azure DNS resolution failures
• Overview of DNS zones and records
• Name resolution for resources in Azure virtual networks

Kindly let us know if the above helps or you need further assistance on this issue.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".