• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 688
  • Last Modified:

Changing DNS settings in DNS Manager Windows Server 2008

Hi,

I have three SharePoint Servers. Two are web frontends and the other is used as the Meta Crawler.

One Web Server is called SharePointWFE1 IP Address 10.168.1.2 and the other is called SharePointWFE2 10.168.1.3.

We have a CNAME setup it's SharePointWFE. The TTL is set to 30 mins for each webserver. I need to patch SharePointWFE1 tomorrow. I know I can change the CNAME entry to SharePointWFE2 however I don't want to wait or lower the TTL. I want users to be able to switch over to the other Web Server straight away.

Is there a way I can change this manually so this chance kicks in straight away? I think the setting is called reload but it's a while since I've done this. Can you please confirm this?

I hard if I do this it might generate a good bit of network traffic
0
makel2
Asked:
makel2
  • 3
  • 2
  • 2
5 Solutions
 
theras2000Commented:
Hmm ... maybe you could use NLB and point your CNAME towards the load-balanced IP.  The tomorrow, you could remove one of your servers from the NLB pool.  You'd obviously want to test this a little.
0
 
Paul MacDonaldDirector, Information SystemsCommented:
We use NLB and just point to the clustered addresses, but in your case you could move the IP address to the second server for the duration of the downtime.  Then remove it before you boot the other machine.  You'll still end up with some downtime, but it should be only a few minutes.
0
 
makel2Author Commented:
How do manually make the change in DNS manager? I don't want to wait for TTL!
0
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!

 
Paul MacDonaldDirector, Information SystemsCommented:
Change the IP address for SharePointWFE1 so it's the same a SharePointWFE2.  Then any traffic for either server will go to SharePointWFE2.
0
 
makel2Author Commented:
What about the end user i want them to see this effect straight away. Do i click the the reload menu?
0
 
theras2000Commented:
I think your suspicions are correct that the client PCs won't re-resolve the IP until the TTL is past.
0
 
Paul MacDonaldDirector, Information SystemsCommented:
Make the change now.  Wait a few hours.  Take down the machine.

...or...

Move the IP address for the first machine to the second machine, like I initially suggested.

...or...

Change the NAT in your router (presuming you do that) to route traffic for the IP address of the first machine to the second machine.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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