Re: First Win2003 Server

Hi,

To rename a Windows 2003 domain, please check following tool:

http://www.microsoft.com/technet/downloads/winsrvr/domainrename.mspx

For the potential issue, I just provide one point:

In your case, we just need to add an A record named WWW. However, if there
is a computer also named WWW in your domain, this method will not work. Go
further, in your scenario, we must add every records in external DNS into
internal DNS(your domain name related records). Otherwise, it will not
forward the query automatical because the domain name is match. For
example, if you host your comany's email server on your ISP side also, we
have to add MX record in internal DNS also.

Thanks.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no rights.
======================================================



--------------------
From: "Ron" <jfkfjdsarewureow@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <O9BLzIfqGHA.2440@xxxxxxxxxxxxxxxxxxxx>
<LnLAJFhqGHA.5740@xxxxxxxxxxxxxxxxxxxxx>
<ubwobnqqGHA.2452@xxxxxxxxxxxxxxxxxxxx>
<OgPSdirqGHA.4992@xxxxxxxxxxxxxxxxxxxx>
<R7v4RVvqGHA.4728@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: First Win2003 Server
Date: Wed, 19 Jul 2006 11:40:57 -0700
Lines: 184
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <#kHqhL2qGHA.3256@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: h-66-134-50-157.lsanca54.covad.net 66.134.50.157
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24495
X-Tomcat-NG: microsoft.public.windows.server.migration

How can we change internal domain name without messing up W2k3 AD? Can it
be
changed without reinstallation?

What potential issues are there besides the one we're having now (unable
to
browse www.ourcompanyname.com)

"Vincent Xu [MSFT]" <v-xuwen@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:R7v4RVvqGHA.4728@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

"our internal (W2k3) domain name is exactly the same as our external
(registered or public) domain name"

That's the problem. If you concern is just cannot resolve the http site,
as
a simplem method, you can add an A record named "www", point it to the
external web site's ip.

However, as a long time consideration, I still suggest you rename
internal
or external domain name to distinguish them. Because there will be
potential issue if they have the same name.

thanks.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no
rights.
======================================================



--------------------
From: "Ron" <jfkfjdsarewureow@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <O9BLzIfqGHA.2440@xxxxxxxxxxxxxxxxxxxx>
<LnLAJFhqGHA.5740@xxxxxxxxxxxxxxxxxxxxx>
<ubwobnqqGHA.2452@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: First Win2003 Server
Date: Tue, 18 Jul 2006 15:22:07 -0700
Lines: 104
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <OgPSdirqGHA.4992@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: h-66-134-50-157.lsanca54.covad.net 66.134.50.157
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24475
X-Tomcat-NG: microsoft.public.windows.server.migration

I forgot to mentioned that our internal (W2k3) domain name is exactly
the
same as our external (registered or public) domain name. Hope that
helps
describe my problem.


"Ron" <jfkfjdsarewureow@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ubwobnqqGHA.2452@xxxxxxxxxxxxxxxxxxxxxxx
I can access ALL internet sites just fine except our own company
website
hosted at our ISP webserver (outside our network). All of our
internal
machines use Win2k3 DNS server for name resolution.

The problem is W2k3 DNS server is the authoritative DNS for our
domain
name
so when we try to access www.ourcompanydomain.com (not the real
name),
W2k3
DNS can't resolve it (there is no record for
www.ourcompanydomain.com)
and
won't forward it to the root hint servers either. To resolve the
problem,
I
must manually add a record in the DNS so that it can forward the
request
to
our ISP web server IP address.

I'm not sure what record to add. That's what my question is.


"Vincent Xu [MSFT]" <v-xuwen@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:LnLAJFhqGHA.5740@xxxxxxxxxxxxxxxxxxxxxxxx
Hi,

From your description, I suspect the symptom is you cannot access
any
web
sites in the Internet.

I think we'd better find some clues from the DNS log. Please
enable
DNS
debug log and send me the log. Please refer to following steps:

1. Open DNS console.
2. Right click the server and choose properties.
3. Click Tab "debug logging"
4. Enable logging and specify the log path.
5. Restart the DNS server.
6. From any client in the domain to access a internet website for
example:
www.google.com
7. Stop the DNS server and send me the log to
v-xuwen@xxxxxxxxxxxxx

Thanks.


Best regards,

Vincent Xu
Microsoft Online Partner Support

======================================================
Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your
newsreader
so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties,and confers no
rights.
======================================================



--------------------
From: "Ron" <jfkfjdsarewureow@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: First Win2003 Server
Date: Mon, 17 Jul 2006 15:41:49 -0700
Lines: 10
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
Message-ID: <O9BLzIfqGHA.2440@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: h-66-134-50-157.lsanca54.covad.net
66.134.50.157
Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:24457
X-Tomcat-NG: microsoft.public.windows.server.migration

I've just added a Windows 2003 server by installing it over NT4
PDC
installation. This machine is then configured as AD controller
and
DNS
server. We now can't browse to company website
(www.our-company-name.com)
hosted by our ISP.

IIRC I saw a KB article @microsoft.com that shows us how to add
a
record
in
the W2k3 DNS server to make it work. I can't remember which
record
to
add
and I can't find that article no more. Help pls. Thanks.














.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... DNS stuff says your mail server is responding with reply that is not MS ... When we setup this new SBS2003 setup we installed without ISA as it does ... not seeing any problems anywhere regards internet or email - we also run ...
    (microsoft.public.windows.server.sbs)
  • Re: Non-domain connection problem
    ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
    (microsoft.public.windows.server.sbs)
  • Re: resolve incorrect IP from RRA server.
    ... dynamic address, 10.5.101.123 from DHCP server. ... This is because the addtional DNS records that get registered cause major problems with AD functionality, especially the additional IPs registered by RRAS. ... However, if you choose to keep RRAS on the DC, then you have to force DNS to only register the internal static interface, and no others. ... If it is the internet gateway, it is recommended to purchase an inexpensive, or cable/DLS router, or even better, a Cisco or similar firewall to perform the task, which if it is compromised by an internet attacker remotely, can further compromise the rest of the internal network. ...
    (microsoft.public.windows.server.dns)
  • Re: Urgent! New router and big disaster
    ... Even a single-NIC configuration should have ONLY the LAN IP of the server as ... Then you can run the CEICW or use the DNS console to enter ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)