Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


  • 6 Major Sites with Server 2003/2008 DCs doing DHCP/AD Integrated DNS, each on their own subnet.
  • All connect back to datacenter through a 3 mbps WAN
  • ERP server running in the datacenter, accessed by clients at all sites

Currently, when we update the software, I manually push a copy of the updated client/config files down to each DC. I have a script that we run on each PC to update the clients. It determines what subnet the PC is on, and pulls the software from that DC.

It's messy, but it works.

The client has an autoupdate feature, but it'll only pull from the application server (which is housed in the datacenter, over the 3 meg link). It takes forever, since the updates are not "patches" but a full version of the client, even for minor upgrades (bad design).

After the most recent patch, you can configure the clients to pull from a different server. Unfortunately, it is the same for all clients.

Is there some kind of DNS magic I can use to pull from the local server? For instance, if I tell the clients their update server is ERPUPDATE, can I have their local DNS server return a different IP for ERPUPDATE than the other sites?

Example: Client 1 is at site A, client 2 is at site b. They each run the software and a version change is detected. As per the config files, the clients look to ERPUPDATE for their updated client.

  • Client 1 queries DNS for the IP of ERPUPDATE at its current location (site A)
  • DNS at site A returns
  • Client 1 pulls update from
  • Client 2 queries DNS for the IP of ERPUPDATE at its current location (site B)
  • DNS at site B returns
  • Client 2 pulls update from

Excuse the poor explanation, I worked 61 hours over the weekend and haven't completely rebounded. I'll be happy to clarify if needed!

share|improve this question
up vote 2 down vote accepted

I use the Active Directory domain name to help localize services, you could put the software updates on a share on each DC. For example if you ping mydomain.local from site A it should automatically resolve to the IP of the DC in site A.

You could place the updates in folder with in netlogon and access it via \\mydomain.local\netlogon\updates

A better option would be to setup DFS replication with a namespace, you can then do \\mydomain.local\updates.

Hope this helps.

share|improve this answer
Good ideas, I'll give those a try! Thanks! – Mike Morris Jan 12 '11 at 16:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.