Then just copy the zone file from the linux server, edit the zone name, and import it into windows.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kurt Buff Sent: Thursday, February 18, 2016 10:58 PM To: [email protected] Subject: Re: [powershell] DNS: pulling records from one zone, entering them into another zone We're getting rid of the zone and name entirely - lab.net is going away, and it's just going to be the production zone - example.com The lab zone is already a secondary in AD, and we could promote it, but we're just not interested in managing two zone. Kurt On Thu, Feb 18, 2016 at 6:23 PM, Michael B. Smith <[email protected]> wrote: > I wouldn't use PowerShell to do this, unless you have more than a handful of > zones to transfer. > > Process: > > Allow zone transfers from the Linux DNS server to the Windows DNS server. > > Create a secondary zone on the Windows DNS server pointing to the primary > zone on the Linux DNS server with the Linux DNS server as the master. > > Reload the zone on Windows (transfer all the zone records from Linux to > Windows). > > Promote the zone on Windows to primary. > > Stop the zone on Linux. > > Remove the zone transfer info from the Windows DNS server. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Kurt Buff > Sent: Thursday, February 18, 2016 9:09 PM > To: [email protected] > Subject: [powershell] DNS: pulling records from one zone, entering > them into another zone > > All, > > We're decommissioning a DNS server in our lab, which had its own zone > - it's a Linux environment, not a Windows environment, so we're not messing > with AD in the lab. > > However, currently our AD DNS servers are secondaries for DNS in the lab. We > wish to copy the A records from the lab zone into the production zone. After > that's accomplished, we will be finish off decommissioning the lab DNS server. > > STFW shows me how to merge zones, which is not what we're after. > > Of course, all of the records we're copying will be static. > > I'm just not seeing how to do this one. > > Naively, I am thinking that something like this would work: > > get-dnsserverresourcerecord -computername usdc01p -zonename > examplelab.com -rrtype A | select hostname, recorddata | > get-dnsserverresourcerecord -zonename testzone.net -computername > usdc01p > > I'm going to stand up a test zone in AD, and try this out. > > If anyone's done something like this, do you know of any particular gotchas? > > Thanks, > > Kurt > > > ================================================ > Did you know you can also post and find answers on PowerShell in the forums? > http://www.myitforum.com/forums/default.asp?catApp=1 > > > ================================================ > Did you know you can also post and find answers on PowerShell in the forums? > http://www.myitforum.com/forums/default.asp?catApp=1 ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1 ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1
