"Mark Levy" <no-m***@nowhere.com> wrote in message
news:%23FDHIy5IGHA.1836@TK2MSFTNGP11.phx.gbl...
> Are there any unforseen ramifications to changing the IP address or name
> of a domain controller?  What about a DC that's also a DNS server.
>
> Obviously, I'll need to change the appropriate entries in DNS, but it's
> been my experience with other directory services, that I've had to run
> certain additional repairs to other replication partners.
>
> Thanks,
>
> Mark
>
>

"Cary Shultz" <cwshu***@mvps.org> wrote in message
news:ODPeMj8IGHA.3120@TK2MSFTNGP10.phx.gbl...
> Mark,
>
> There should not be any problems with giving it a new IP Address
> (naturally assuming that this IP Address is not part of any DHCP Scope
> that might be given out to a DHCP Client).  Just make sure that the new IP
> Address is part of the correct Site (as defined by the Active Directory
> Sites and Services) and that you manually verify that all has happened as
> it should.
>
> I would also suggest that you run the following from a command prompt
> after you change the IP Address:
>
> net stop netlogon
> ipconfig /flushdns
> ipconfig /registerdns
> net start netlogon
>
> Do you have the Support Tools installed on this Domain Controller?  I am
> pretty sure the netdiag /fix could help as well.
>
> --
> Cary W. Shultz
> Roanoke, VA  24012
>
> "Mark Levy" <no-m***@nowhere.com> wrote in message
> news:%23FDHIy5IGHA.1836@TK2MSFTNGP11.phx.gbl...
>> Are there any unforseen ramifications to changing the IP address or name
>> of a domain controller?  What about a DC that's also a DNS server.
>>
>> Obviously, I'll need to change the appropriate entries in DNS, but it's
>> been my experience with other directory services, that I've had to run
>> certain additional repairs to other replication partners.
>>
>> Thanks,
>>
>> Mark
>>
>>
>
>

"Mark Levy" <no-m***@nowhere.com> wrote in message
news:%23FDHIy5IGHA.1836@TK2MSFTNGP11.phx.gbl...
> Are there any unforseen ramifications to changing the IP address or name
> of a domain controller?  What about a DC that's also a DNS server.
>
> Obviously, I'll need to change the appropriate entries in DNS, but it's
> been my experience with other directory services, that I've had to run
> certain additional repairs to other replication partners.
>
> Thanks,
>
> Mark
>
>

news:u0ZMVJAJGHA.3492@TK2MSFTNGP09.phx.gbl...
> before configuring the new IP address, first determine which
> functionalities/services are being provided by the server that should get
> a new IP.
> After that determine for each service how it is used by other clients and
> servers.
> An example:
> If that server hosts DNS that could mean:
> * Clients reference that server from their TCP/IP DNS settings provided by
> DHCP (so you need to change the DHCP options)
> * Servers reference that server from their TCP/IP DNS settings (so you
> need to change the TCP/IP DNS settings )
> * The DNS service itself registers record in DNS so you would need to
> restart the DNS service
>
> etc.
>
>
>
>
> --
>
> Cheers,
> (HOPEFULLY THIS INFORMATION HELPS YOU!)
> # Jorge de Almeida Pinto #
> MVP Windows Server - Directory Services
> BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
> -----------------------------------------------------------------------------
> * This posting is provided "AS IS" with no warranties and confers no
> rights!
> * Always test before implementing!
> -----------------------------------------------------------------------------
>
>
> -----------------------------------------------------------------------------
> "Mark Levy" <no-m***@nowhere.com> wrote in message
> news:%23FDHIy5IGHA.1836@TK2MSFTNGP11.phx.gbl...
>> Are there any unforseen ramifications to changing the IP address or name
>> of a domain controller?  What about a DC that's also a DNS server.
>>
>> Obviously, I'll need to change the appropriate entries in DNS, but it's
>> been my experience with other directory services, that I've had to run
>> certain additional repairs to other replication partners.
>>
>> Thanks,
>>
>> Mark
>>
>>
>
>