Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Moving Win2K Server to new location - What DNS changes are needed?
- Thread starter bidbear
- Start date
BigShyBear
MIS
Depends on what is running, and what is at new site.
If this server is NOT an e-mail server, and NOT an internet accessible web server, then maybe nothing needs to be changed. There are a number of maybes.
Checklist:
1. Is this server running Exchange (or other e-mail service?)
2. Is this the only server?,
a. Is it providing DHCP?
Is there another device at the new site providing DHCP?
b. Is it providing DNS?
inside?
outside?
3. Is this a web server for an internet side web site or sites?
4. Is there an Internet access router at the new site that you do not have control over - and you cannot change the inside IP address?
--------------------------------------
Partial answers:
1. If this server is running e-mail, add an MX record and an A record for the new location.
2. a. Check the IP address of the default gateway. (2 places, in DHCP and in the IP configuration for the NIC on the server.?)
b. Is the server configured as a root server, or does it have DNS forwarders configured? Sometimes ISP's block DNS queries to other ISP's DNS servers. You may have to change your forwarders to their DNS servers. Also you should check the DNS servers configured in the IP configuration on the NIC in the server. If you are running Active Directory, the DNS address needs to be pointed back to itself.
If you are providing DNS for outside, you need to check the firewall at the new location and verify that it allows DNS queries through to the server. Most of the time this means port forwarding UDP on port 53.
3. If it is an internet accessible web server, you'll need to verify the firewall at the new site is allowing HTTP (and possibly HTTPS) requests through to the server, and change the A record in DNS for the web server. And you'll need to wait while dns caches around the internet purge the old address out, and pick up the new one.
4. Firewall router at the new site will have an inside IP address configured, this will almost certainly be your default gateway. If you can't change this address to agree with the address of your old firewall router, then you'll need to change the IP address scheme on the new network.
If you are NOT providing outside DNS, e-mail and web service then the change over is simple.
Provide us with more details and we can give you exact answers.
If this server is NOT an e-mail server, and NOT an internet accessible web server, then maybe nothing needs to be changed. There are a number of maybes.
Checklist:
1. Is this server running Exchange (or other e-mail service?)
2. Is this the only server?,
a. Is it providing DHCP?
Is there another device at the new site providing DHCP?
b. Is it providing DNS?
inside?
outside?
3. Is this a web server for an internet side web site or sites?
4. Is there an Internet access router at the new site that you do not have control over - and you cannot change the inside IP address?
--------------------------------------
Partial answers:
1. If this server is running e-mail, add an MX record and an A record for the new location.
2. a. Check the IP address of the default gateway. (2 places, in DHCP and in the IP configuration for the NIC on the server.?)
b. Is the server configured as a root server, or does it have DNS forwarders configured? Sometimes ISP's block DNS queries to other ISP's DNS servers. You may have to change your forwarders to their DNS servers. Also you should check the DNS servers configured in the IP configuration on the NIC in the server. If you are running Active Directory, the DNS address needs to be pointed back to itself.
If you are providing DNS for outside, you need to check the firewall at the new location and verify that it allows DNS queries through to the server. Most of the time this means port forwarding UDP on port 53.
3. If it is an internet accessible web server, you'll need to verify the firewall at the new site is allowing HTTP (and possibly HTTPS) requests through to the server, and change the A record in DNS for the web server. And you'll need to wait while dns caches around the internet purge the old address out, and pick up the new one.
4. Firewall router at the new site will have an inside IP address configured, this will almost certainly be your default gateway. If you can't change this address to agree with the address of your old firewall router, then you'll need to change the IP address scheme on the new network.
If you are NOT providing outside DNS, e-mail and web service then the change over is simple.
Provide us with more details and we can give you exact answers.
- Status
Similar threads
- Locked
- Question
- Locked
- Question