Announcement

Collapse
No announcement yet.

Process check, migrating a domain to new subnet

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Process check, migrating a domain to new subnet

    Good afternoon everyone,

    This my current gammit to run.

    I currently have the following setup:
    2 DCs that are 2003 SP1 (Native 2003 Server mode)
    Both of my DCs are GCs, both host ADI DNS.
    I have two class C /24 subnets that my servers, printers and hosts are on.
    All servers, hosts and printers are set with a static address


    I am getting a new router as well as a Class C /21 network.
    I need to migrate everything to the new subnet and push all hosts (no servers or printers) to DHCP. My plan is as follows:

    -Change DNS from ADI to a Primary Standard
    -Backup DNS
    -Create a new DNS zone, modify both DCs IPs, A records and NS records in the new zone
    -Setup a new DNS Reverse zone
    -Integrate the new zone into Active Directory
    -Create a DHCP scope, excluding the range for printers and servers.
    -Change each host to DHCP, reboot
    -Change each printer IP on the print server (only 40) to the new IP. Hand jam each printer to the new IP, reboot printer.
    --------------------------------------------------
    Post initial windows migration
    -Change all remaining Servers IPs
    -Change all remaining switch IPs
    -Change all application pointers and clients

    Does this process sound concrete or is there anything I'm forgetting or shouldn't be doing?

    Thank you for any assistance!

    Fahl

  • #2
    Re: Process check, migrating a domain to new subnet

    sounds like something that should work, except for one thing. What is the need to mess around with DNS? Obviously you need a new reverse zone if you go to a new IP schema, but why are you changing scope of the forward zones, deleting, etc?

    Comment


    • #3
      Re: Process check, migrating a domain to new subnet

      Thanks for the reply wkasdo,

      My reasoning behind DNS removal is that I have a zone that is filled with static records, these records are also not set to be pruned.

      I would think creating a new zone that DHCP updates (both foward and reverse) with dynamic entries would create a clean zone.

      Now that I am thinking about what you said, pehaps the best method would be to delete all of the static entries and turn DHCP on and let it repopulate my current DNS zone. I know it would be easy to find the old entries since they are 198.x.x.x and the new ips would fall under 205.x.x.x.

      I think this is what you were getting at, am I correct?

      Comment


      • #4
        Re: Process check, migrating a domain to new subnet

        For cleaning up the static records from a given zone, give a shot to the BATCH script attached
        Attached Files
        Last edited by guyt; 10th November 2005, 21:04.
        Guy Teverovsky
        "Smith & Wesson - the original point and click interface"

        Comment


        • #5
          Re: Process check, migrating a domain to new subnet

          btw, you can extend the script to create new static entries with new IPs, if you want to, but in your case, I'd stick to dynamic DNS if we are talking about W2K and above machines.
          Guy Teverovsky
          "Smith & Wesson - the original point and click interface"

          Comment


          • #6
            Re: Process check, migrating a domain to new subnet

            > I think this is what you were getting at, am I correct?

            Correct!

            Out of curiosity, why don't you use a private IP range since you are renumbering anyway?

            Comment


            • #7
              Re: Process check, migrating a domain to new subnet

              Thank you very much for your help wkasdo and guyt,
              I will give it a shot.

              I am not using private subnets do to my customer's operation requirements.

              Comment

              Working...
              X