I need to consolidate some reverse lookup zones to - need very basic process?

I need to consolidate some reverse lookup zones and I need a process for this - servers are 2008 r2 datacenter.
Export list does not export anything (never opens a file location to save data)
I have googled and have not found anything that fits our particular situation - we have non active directory zones and will be transitioning to hardened enterprise appliances for DNS and (DHCP by the way)
Consolidating the zones would make it easier to manage at the moment.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

FlyboyExch60Author Commented:
Ok - I was just able to use export list to export the content of the reverse lookup zones - now need some script to import and consolidate into the
Will SzymkowskiSenior Solution ArchitectCommented:
You can use the dnscmd command to import/export zones. Take a look at the KB article which outlines the correct syntax for this.

You can also do this from powershell (not natively) but with DNSShell (2012R2 you can do this natively)

DrDave242Senior Support EngineerCommented:
I've been doing some testing. Here's a high-level procedure that worked for me (I'll go ahead and tell you, steps 2 and 3 will likely take a while unless you're good with scripts for modifying text files):


First, exporting the data isn't necessary if the zones aren't AD-integrated; they're already stored in text files in the Windows\System32\dns folder. Make a copy of one of those zone files and call it newzone.txt or something like that.


Add the necessary octets to the existing PTR records in newzone.txt to make them compatible with the consolidated zone, and remember that they'll go in reverse order. For example, if the previous zone was for the range and the new zone is for, you'll have to append .1.2 to each entry. (100 PTR host1.domain.com. becomes 100.1.2 PTR host1.domain.com.) If you've got a large number of records and some scripting expertise, you'll want to script this.


Copy the PTR records from the other zones into newzone.txt, adding their respective octets.


Create the new reverse lookup zone on your DNS server. Make it a standard primary zone, not AD-integrated.


Copy the PTR records from newzone.txt into the zone file that corresponds to the new zone.


Right-click the new zone in the DNS console and select Reload. The PTR records you copied into the zone file should appear in the console. A refresh may be necessary.


Delete the old zones when you're satisfied that the new zone looks good.
You can now make the new zone AD-integrated if you want to, but since you stated you'll be using a DNS appliance in the future, that's probably not necessary. When the time comes to copy the zone to the appliance, just configure a zone transfer to do the job.

If you want more details on any of the steps (except the scripting part - that's not my strong suit), feel free to ask.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

FlyboyExch60Author Commented:
DrDave - this is part of what is in the zone file at windows\system32\dns

;  Database file 1.110.10.in-addr.arpa.dns for 1.110.10.in-addr.arpa zone.
;      Zone version:  205

@                       IN  SOA machine01.xxxx.local. hostmaster.xxxx.local. (
                                    205          ; serial number
                                    900          ; refresh
                                    600          ; retry
                                    86400        ; expire
                                    3600       ) ; default TTL

;  Zone NS records
I see no IPs in the file - can I just add the heading and IPs in the exported file that I got from each reverse lookup zone?
DrDave242Senior Support EngineerCommented:
Is there a "Zone records" section at all? That's where the PTR records should be.
FlyboyExch60Author Commented:
I am still struggling with this solution
DrDave242Senior Support EngineerCommented:
Can you be more specific about what you're having trouble with?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.