Modify nameserver for domain clients with GPO

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello all,

Does anyone know if its possible to change the primary and secondary DNS
settings for domain client PCs via a (2000 Server) GPO? Or, possibly with a
KiX script? (I figured user permissions might be an issue with the latter)

Thanks
Maurice
 
Howdie!
Does anyone know if its possible to change the primary and secondary DNS
settings for domain client PCs via a (2000 Server) GPO? Or, possibly with a
KiX script? (I figured user permissions might be an issue with the latter)
Click to expand...

I wonder why you want to do that. Changing the DNS server of the clients
might break your domain services like login and Group Policies. Is it
really necessary to change the DNS? Would setting the DNS server via
DHCP be an alternative for you?

cheers,

Florian
 
Florian Frommherz said:
Howdie!


I wonder why you want to do that. Changing the DNS server of the clients
might break your domain services like login and Group Policies. Is it
really necessary to change the DNS? Would setting the DNS server via
DHCP be an alternative for you?

cheers,

Florian
Click to expand...

Hi Florian,

All of our PCs are configured with static IP and DNS addresses, and the DNS
server they are set to is being retired (which is actually a Bind box). The
new DNS servers are the domain controllers, which are already configured and
running properly.
 
Hi,
Does anyone know if its possible to change the primary and secondary DNS
settings for domain client PCs via a (2000 Server) GPO? [...]
Click to expand...

Computer Startup script and netsh.
-> netsh interface ip set dns "name of your connection" static d.d.d.d

But I share possible problems, that Florian mentioned.

Mark
 
Check on the ScriptCenter as they have brief sample code
to handle this. There is policy to set client DNS suffix
search list, but not server list. Sort of a catch-22. If not
using a DNS server able to support domain group policy
would not be applying correctly.
The issue you will encounter adapting from the scripts at
www.microsoft.com/technet/scriptcenter is that there may
be parameters that will be unique per machine, as this tends
to be set in the per-interface parameters for each within the
Tcp/Ip reg keys, so your startup script may need to first
acquire this info.
 
Back
Top