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
If you have two DNS Zones with similar names i.e.(www.example.com and example.com) and you try to do a simple filter of DNS Zones using the where-object cmdlet, the expected result of returning the only one name is not achieved, instead you get both names, this is the case no matter which case you filter for, this can also be seen for the etag property of the DNSZone Object.
@animetauren Hey Henry, thanks for reporting this. We will have a PR out shortly that will fix this issue (just a matter of using the enumerateCollection parameter in this WriteObject call).
As a workaround until we get this fix in the next release next Friday, you can do
Cmdlet(s)
Get-AzureRmDnsZone
PowerShell Version:
5.1.15063.413
Module Version
AzureRM.Dns v3.1.0
OS Version
10.0.15063.413
Description
If you have two DNS Zones with similar names i.e.(www.example.com and example.com) and you try to do a simple filter of DNS Zones using the where-object cmdlet, the expected result of returning the only one name is not achieved, instead you get both names, this is the case no matter which case you filter for, this can also be seen for the etag property of the DNSZone Object.
Script/Steps for Reproduction
Get-AzureRmDnsZone | Where-Object {$_.Name -eq "example.com"}
The text was updated successfully, but these errors were encountered: