Re: domain rename

From: John (John_at_discussions.microsoft.com)
Date: 11/18/04 

Date: Thu, 18 Nov 2004 14:03:05 -0800

Thanks Kevin, your answers were helpful. Yeah it is a third level .com domain
where it is going to be customer.company.com.

So, I think it should not be a problem. Since, at a later stage when they
integrated it with the main Forest, they would want to move all this to the
company.com domain. At present it is internal and it is within a private
network/VPN you can say.

thanks

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> In news:287842E5-1AA2-495C-A4A8-1656974ED78F@microsoft.com,
> John <John@discussions.microsoft.com> commented
> Then Kevin replied below:
> > Thanks Kevin,
> >
> > Now, I have another question. Once I Raise the functional
> > level to be Windows Server 2003. Will there be any
> > problems with those servers in another site that are
> > under Win2K domain and member servers accessing these
> > servers, shares etc.. I just want to be cautious before I
> > do this change.
>
> If there are any DCs in the forest still running Win2k you won't be able to
> raise the functional level. If the servers you are talking about are in
> another forest it won't cause a problem.
>
> >
> > Since, the other network is at the customer site and they
> > run Win2K domain controller and member servers. Couple of
> > servers will try to access the shares on these member
> > servers and also there might be a possibility of a trust
> > relationship that may be established. So, just want to
> > know earlier.
> >
> > And moreover I looked into the domain rename document and
> > found that once you run the rendom /list command it
> > creates a xls file and I have to do the modifications on
> > the xls file and upload it back using the rendom command,
> > am i correct? and this should take care of the issue?
>
> I don't know about this question.
>
> > Also, what I am trying to achieve here is that renaming
> > an existing .local to .com which is what the client wants.
>
> There can be serious drawbacks to using a .com TLD especially if they have
> VPN clients. If the have VPN clients and they really must use the .com TLD,
> then I would suggest changing the name to a third level .com name like
> ad.domain.com. Then delegating the sub domain from the public name space, if
> they have one, to the private addresses of the internal DNS servers in the
> internal domain.
>
>
> --
> Best regards,
> Kevin D4 Dad Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>

Relevant Pages

  • Re: Slow DNS lookup
    ... Thanks Ace for taking your time to drop in. ... I have already disabled forwarders on my server and are now only using ... using those addresses Kevin gave me. ... > content only DNS servers and will not resolve queries ...
    (microsoft.public.win2000.dns)
  • Re: Evict and Swap nodes possible?
    ... Kevin ... >> on other servers without any problems. ... If the mix mode works then I'll give that a shot. ... >>> Ryan Sokolowski ...
    (microsoft.public.windows.server.clustering)
  • Re: https & update problems in W2K3 SP1
    ... If I go through Help and Support to windowsupdate, ... "Kevin D. Goodknecht Sr. ... Other servers (we use same firewall settings ...
    (microsoft.public.windows.server.security)
  • Re: Slow DNS lookup
    ... Peter Schou made a post then I commented ... > forwarders you suggested in a previous post. ... Just wanted to jump in and add that what Kevin is trying to say is that the ... than the zones that were created in their own DNS servers). ...
    (microsoft.public.win2000.dns)
Quantcast