[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 203
  • Last Modified:

Moving Windows Server 2003 to a new Machine, DNS issues

We currently have a windows server 2003 machine running dns, email, print, and sql servers for our office.  The original installation, however, was rather buggy and rushed so we are looking to set up a temporary machine to run things and avoid downtime while we wipe and reinstall the main server.  So far I have email and sql server running fine on the temporary machine and I'm sure print stuff won't be much of an issue.  What I'm not sure about is the DNS side of things.  The original server controlled the domain pkal.local and the temporary one is on pkal1.local .  If I cut the main server out of the loop, internet access goes down.  What do I have to do to get the temporary one running dns?  Are there any other things to consider before wiping the main server and starting over?
0
warrenpeace3
Asked:
warrenpeace3
1 Solution
 
Andrew DavisManagerCommented:
You would need to ensure that the forward lookups are in for your ISP and that the clients are looking in the right location from the DHCP. Also it reads like you have setup the temporary server on a complete new domain pkal1. Why would you do this. why not just make the new server a DC on the existing domain and then cut all the services over to it. Then rebuild your main server and switch back?
0
 
Andrew DavisManagerCommented:
0
 
warrenpeace3Author Commented:
When I was setting it up, there were issues setting up the temporary server on the same domain.  Given a second chance, with a now more informed understanding of the matter, I would do it as you suggested.  Any way to rectify this issue now after the fact?
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
Andrew DavisManagerCommented:
Depends how far into it you are, and how much work is involved in changing everything. It would involve blowing away the new DC and starting again. but if you are not talking about a LOT of users and you can manage the headaches (joining clients to new Temp domain, then rebuild original domain and rejoin them to new fresh domain, then this may be the way to go).

Or you could dcpromo demote your test server to a member server, join it to the existing domain, then dcpromo it in the new domain. Let the dc sync, and start moving services as required till you can power off the existing server. Then rebuild and join it to the existing domain and transfer services back.
0
 
KCTSCommented:
The recommended way to install Active Directory with DNS is to use an Active Directory Integrated DNS Zone. This makes life simpler by integrating these two technologies and provides greater flexibility and security than is possible with 'traditional' DNS.

The simplest way to create AD with AD Integrated DNS when setting up a new doamin domain is to simply run DCPROMO from the RUN command and when When windows prompts you, allow windows to install DNS - it will create an AD Integrated DNS by default.

Once you have your Domain Controller operational, then you must make sure that all the machines point to your Windows DNS Server (the DC), as the preferred DNS server. If you only have one Domain Controller, the alternate DNS server should be blank. The DNS server settings can e set via DHCP options ot in the TCP/IP properties on each machine.

In order to resolve external names to IP addresses, you will need to open up the DNS server console on the DC, right ckick on the server and select properties, and then on the forwarders tab enter the IP address(s) of your ISPs DNS server(s).
0
 
kmotawehCommented:
try to install the dns on the new server and make active directory integrated and if you use a dhcp server configure it to publish the ip address of the new server as the primary dns server
0
 
Andrew DavisManagerCommented:
Thanks for the points.
How did you go Warren, did you end up blowing away and starting again?
0
 
warrenpeace3Author Commented:
Yeah - I finally realized how messed up the installation had been on the second server and decided to fix all of that so the dns and such lined up better.  Thanks for the pointers.
0
 
Andrew DavisManagerCommented:
yeah i have suffered too many times from trying to fix up problem after problem from a bad initial config, that now days i dont give it too much thought and find clients accept that the reason they got me in is because of all the issues, so once you explain that if you simply fix the ones you can see then you will allways be finding little errors pop up. so the inconveniance of a full clen rebuild gives a lot of hurt initially, but in the long run it is the best.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now