Actually, MS DNS works the same way as long as you're running from standard boot and zone files and not the registry. In fact I've even moved from BIND to MS and from MS to BIND with very few changes required. I mirror our DNS (rather than setting up secondaries) by simply copying all of these files (I'm talking thousands of zones) from one server to another.
Dermot -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kevin Bilbee Sent: Thursday, October 20, 2005 11:40 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] OT: New DNS Server This is exactly why we use BIND and not MS DNS for our public facing DNS. All you need to do to migrate to a new server is change a few ip addresses (if changing IP addresses) in a text based file. Then copy that to the new server and off you go. Kevin Bilbee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Darin Cox Sent: Thursday, October 20, 2005 5:58 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] OT: New DNS Server We do something like the script below for out secondaries. We store all zones in a database and have stored procedures that do all of the heavy lifting to create the zones on primary and secondary servers. A wonderful time saver when migrating servers... run a cursor, or script, over the list of domain names and viola... two minutes later you have a complete nameserver. Darin. ----- Original Message ----- From: Andy Schmidt To: Declude.JunkMail@declude.com Sent: Thursday, October 20, 2005 8:47 AM Subject: RE: [Declude.JunkMail] OT: New DNS Server I have done this in two ways. You can export the registry and then use an editor that can handle line breaks and other control characters (such as MS Words) to massage the text file before reimporting it on the new server. Or, you can create a list of domains (using the DNS command line tools) and then use a little .CMD procedure to create the secondary domain for all these domain names. Here is a sample batch script (mm.mm.mm.mm is the IP of your primary DNS server, nn.nn.nn.nn are the IP addresses of other subordinate DNS servers to which you permit zone transfers) @ECHO OFF if %1.==. goto error01 @ECHO ON DNSCMD \\YOURSERVER /ZoneAdd %1 /Secondary mm.mm.mm.mm /file %1.dns DNSCMD \\YOURSERVER /ZoneResetSecondaries %1 /SecureList nn.nn.nn.nn nn.nn.nn.nn @ECHO OFF :Done GOTO :EOF :error01 ECHO. ECHO Missing Parameters! ECHO. ECHO Syntax: CreateSecondary domainname ECHO Example: CreateSecondary MyDomain.com PAUSE Missing Parameters GOTO :EOF Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax: +1 201 934-9206 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evans Martin Sent: Thursday, October 20, 2005 01:14 AM To: Declude.JunkMail@declude.com Subject: [Declude.JunkMail] OT: New DNS Server Im running Windows 2003 and MS DNS on my primary name server. Now I need to slave another server to it. What is the quickest way to transfer all of the domains from my old server to my new one and change them all from master to slave zones? Thanks, Evans Martin --- Evans L. Martin AIM: martek01 http://[EMAIL PROTECTED] Fax: 615-523-1679 Mobile: 615-533-0197 --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
