I replied in answer to this thread, and then had a thought. In my previous
job, I had the problem I described in the other mail where by my server name
and domain names were different (server.domain.com in the domain
location.domain.com) this meant that everytime we tried to add anything to
that domain, the no domain controller could be found error popped up.
Am I right in guessing that if I had of made the appropriate changes in DNS
to point all applicable SRV records to server.domain.com, that I would have
effectively solved my problem, even thought the domain in the computer name
did not match the actual DNS domain name? Is that clear as mud?
As it was dealt with months ago, it is not an issue to me now, but having
gone through a lot of work to get my network sorted out at the time, I am
very curious to know if I could have got around it in the way I have just
thought of.
Clayton Doige
IT Manager MCSE, MCP + I
Gameday International N.V.
Bound in a nutshell, King of infinite space...
T: +5 999 736 0309
C: +5 999 563 1845
F: +5 999 733 1259
E: [EMAIL PROTECTED]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 11:02 AM
To: NT System Admin Issues
Subject: RE: Upgrading from NT Domain to Win2K Domain
We choose to make ours slightly different internally. Using your example our
external in widgets.com and our internal root is internal.widgets.com. From
that root placeholder we then built our domestic and international domains
where the users and resources are. So our domestic internal domain is
domestic.internal.widgets.com for example.
Thanks
Diane Beckham
<diane.beckham@dptechn To: "NT System Admin
Issues"
ology.com>
<[EMAIL PROTECTED]>
cc:
08/22/2001 10:26 AM Subject: RE: Upgrading
from NT Domain to Win2K Domain
Please respond to "NT
System Admin Issues"
>From what I have read (I haven't done it yet, but I will), that is what MS
recommends, just so you can make it easy for your users.
Diane
-----Original Message-----
From: Montagna, Mark [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 5:57 AM
To: NT System Admin Issues
Subject: Upgrading from NT Domain to Win2K Domain
Hello all,
I actually sent this yesterday, but I wanted to rephrase a few things.
When upgrading our NT Network to a 2000 Domain, we are trying to
understand if we need to distinguish our internal network domain name
from our external FQDN www.widgets.com. For example in NT our current
internal domain name is "widgets" and our external website is
widgets.com. When we upgrade to Win2k what are the ramifications of
keeping our internal 2000 domain "widgets.com" and our external FQDN,
widgets.com. Should we change our internal domain to widgetscorp.com or
something comparable when we upgrade to win2k, and if we don't what
happens. Widgets.com is currently hosted on our internal NT domain on
an
IIS 4.0 server, behind a raptor firewall, using redirection on the
firewall, with DNS at our ISP. Once upgraded to 2000 it will continue
to
be located internally on our network behind the firewall with AD
integrated DNS internally and external internet DNS at our ISP. Thanks
for any help or suggestions in advance.
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
