Export-DnsServerZone -Filename parameter doesn't accept literal file path. - by wolffhaven45

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 790157 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/14/2013 12:04:03 AM
Access Restriction Public

Description

Hi Guys,

Not sure if I have stumbled on a bug or whether it's just user error :D or whether it is by design.

When using the Export-DnsServerZone cmdlet, when I type in: 

Export-DnsServerZone -Name "mydomain.com" -Filename "exportdomain.txt"

it all works.

If I try to use a literal path for example:

Export-DnsServerZone -Name "mydomain.com" -Filename "C:\exportdomain.txt"

I get the following error: 

Export-DnsServerZone : Failed to export the zone content for <yourdomain> on server <yourserver> to the file C:\exportdomain.txt.

If I use a literal path, for example.

Export-DnsServerZone -Name "mydomain.com" -Filename "..\..\..\exportdomain.txt"

that works, and creates the file in the root of C:\.

I've also tried using a UNC path and I haven't had any luck.
Sign in to post a comment.
Posted by Microsoft on 6/18/2013 at 3:33 PM
This is not an issue in core PowerShell. Please log this issue on the DNS Connect site.