Describe the bug The AzDanglingDomain PowerShell module reported a subdomain (CNAME record, format sub.sub2..com) as a dangling DNS record in its scan output. This is a false positive — the record currently resolves to a live target hosted in Azure, so it is not dangling/takeover-vulnerable.
Reproduce Steps to reproduce the behavior:
Run the AzDanglingDomain module's scan against the DNS zone/subscription containing the affected record.
Review the generated report.
Locate the flagged CNAME record in the list of dangling domains.
Note that the record has an active Azure target, contradicting the "dangling" classification.
Expected behavior The record should not be flagged as dangling, since it points to a live, provisioned resource in Azure and is not eligible for subdomain takeover.
Describe the bug The AzDanglingDomain PowerShell module reported a subdomain (CNAME record, format sub.sub2..com) as a dangling DNS record in its scan output. This is a false positive — the record currently resolves to a live target hosted in Azure, so it is not dangling/takeover-vulnerable.
Reproduce Steps to reproduce the behavior:
Run the AzDanglingDomain module's scan against the DNS zone/subscription containing the affected record.
Review the generated report.
Locate the flagged CNAME record in the list of dangling domains.
Note that the record has an active Azure target, contradicting the "dangling" classification.
Expected behavior The record should not be flagged as dangling, since it points to a live, provisioned resource in Azure and is not eligible for subdomain takeover.