DNS Windows 2000 Server

[Keith]

Our web site is hosted by a third party company and is
named www.mydomain.com Prior to Win2k Server, the clients
DNS Entries pointed to IP's that the ISP gave us. When I
upgraded from NT4.0 Server to Win2K Server, I had to
install DNS on the Domain Controller. For Conversation,
our NT Domain was called DOMAIN. Being a rookie at DNS,
during the install, I somewhere typed in the mydomain.com
domain name somewhere. Keep in mind, we do NOT host our
web site. Also during that install, I know I keyed in the
IP's of our ISP for DNS...somewhere somehow. When I
install Win2000 Professional and XP Pro clients, in order
to add the computer to the domain, I need to point their
DNS entries to the Windows 2000 Servers IP Addresses.
(192.168 range) Everything works great, they access our
network and they can access the Web over our T1. HOWEVER,
the ONLY web site they can't get to is our own. If I go
to the XP or Win200 client and change their IP's back to
the ones the ISP gave us, the web site pops right up, but
if I use the DNS of our local Windows 2000 server, it
can't find the web site. I know I have to do something
inside DNS on our Domain Controllers, but I don't know
what. Thanks! Keith

 

[Kevin D. Goodknecht [MVP]]

In

Our web site is hosted by a third party company and is
named www.mydomain.com Prior to Win2k Server, the clients
DNS Entries pointed to IP's that the ISP gave us. When I
upgraded from NT4.0 Server to Win2K Server, I had to
install DNS on the Domain Controller. For Conversation,
our NT Domain was called DOMAIN. Being a rookie at DNS,
during the install, I somewhere typed in the mydomain.com
domain name somewhere. Keep in mind, we do NOT host our
web site. Also during that install, I know I keyed in the
IP's of our ISP for DNS...somewhere somehow. When I
install Win2000 Professional and XP Pro clients, in order
to add the computer to the domain, I need to point their
DNS entries to the Windows 2000 Servers IP Addresses.
(192.168 range) Everything works great, they access our
network and they can access the Web over our T1. HOWEVER,
the ONLY web site they can't get to is our own. If I go
to the XP or Win200 client and change their IP's back to
the ones the ISP gave us, the web site pops right up, but
if I use the DNS of our local Windows 2000 server, it
can't find the web site. I know I have to do something
inside DNS on our Domain Controllers, but I don't know
what. Thanks! Keith

In your local DNS server's forward lookup zone for your domain create a new
host named www with the IP of your web site.

 

[Michael Johnston [MSFT]]

Create a host record called "www" in mydomain.com on the dns server and point it to the IP address of the website. Now the
internal clients will be able to access the page.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[Guest]

Thanks guys. I found that portion of DNS pretty easily
and successfully added a new host with the IP Address of
our web site, but still can't display it on clients that
have the 192.168.....as their DNS servers. Remember, when
I upgraded to Win2000 Server, I did key in our web site
domain name in the Windows 2000 server domain name if that
makes any sense and may be a problem. Our NT4.0 domain
was called something else.
Keith

 

[Kevin D. Goodknecht [MVP]]

In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:

Thanks guys. I found that portion of DNS pretty easily
and successfully added a new host with the IP Address of
our web site, but still can't display it on clients that
have the 192.168.....as their DNS servers. Remember, when
I upgraded to Win2000 Server, I did key in our web site
domain name in the Windows 2000 server domain name if that
makes any sense and may be a problem. Our NT4.0 domain
was called something else.
Keith

So did you add the record for www to your internal DNS forward lookup zone?
If you want to access the web site by just mydomain.com that requires a
blank record but that can cause problems. If that is your question let me
know.

 

[Guest]

Here are the exact names so I'm not confusing you. Our
NT4.0 Domain was named RITZ_CRAFT (that' an underscore,
not a hyphen). We did NOT use DNS internally and our web
site www.ritz-craft.com (with a hyphen) was hosted by an
ISP. I upgraded to Win2000 Server, installed DNS, and
somewhere entered ritz-craft.com as a domain during the
upgrade. DNS is running on the server and all Win2k
clients and XP Pro clients DNS entries point to our main
server 192.168.100.2 in order to join the domain, etc.
All other clients point to our ISP for internet access as
far as DNS 216.169...... etc. After the Win2k and XP
clients join the domain, I can change their DNS entries to
point to the ISP and the web site works. But any Win2k
clients and XP clients that have their DNS entries
pointing to 192.168.100.2 can not view that web site and
that web site only. My computer (network admin) needs the
local DNS to perform admin functions. I went to the DNS
server and added a new host in the Forward Lookup Zone and
named it www and entered the IP Address of our web site
(216.214.52.237) and it said it added successfully but I
still can't view our web site from my PC.
Thanks again.
Keith

-----Original Message-----
In (e-mail address removed)

 

[Kevin D. Goodknecht [MVP]]

In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:

I went to the DNS
server and added a new host in the Forward Lookup Zone and
named it www and entered the IP Address of our web site
(216.214.52.237) and it said it added successfully but I
still can't view our web site from my PC.
Thanks again.
Keith

Where did you get that IP for your web site?
When I do a lookup that is not the IP I get.
W:\>nslookup
Default Server: kjweb.lsaol.com
Address: 192.168.0.2

www.ritz-craft.com

Server: kjweb.lsaol.com
Address: 192.168.0.2

Non-authoritative answer:
Name: www.ritz-craft.com
Address: 66.109.229.34

Maybe your ISP is one of those that likes changing IPs you can instead of a
host use a delegation named www pointing to the authoritative DNS servers
Which are:
Non-authoritative answer:
ritz-craft.com nameserver = ns1.ceinetworks.com
ritz-craft.com nameserver = ns2.ceinetworks.com

ns1.ceinetworks.com internet address = 216.169.160.2
ns2.ceinetworks.com internet address = 216.169.160.23

 

[Guest]

Kevin:
I think we've got it. You're right, the IP Address of
www.ritz-craft.com has changed. I'll try and find out
why. I deleted that DNS lookup entry and added a new one
with the new address, and it worked! I'll assume I need
to add that host to both of our DNS servers.
Thanks again!
Keith

-----Original Message-----
In (e-mail address removed)

 

[Kevin D. Goodknecht [MVP]]

In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:

Kevin:
I think we've got it. You're right, the IP Address of
www.ritz-craft.com has changed. I'll try and find out
why. I deleted that DNS lookup entry and added a new one
with the new address, and it worked! I'll assume I need
to add that host to both of our DNS servers.
Thanks again!
Keith

Try the delegation.

 

[Ace Fekay [MVP]]

In

Here are the exact names so I'm not confusing you. Our
NT4.0 Domain was named RITZ_CRAFT (that' an underscore,
not a hyphen). We did NOT use DNS internally and our web
site www.ritz-craft.com (with a hyphen) was hosted by an
ISP. I upgraded to Win2000 Server, installed DNS, and
somewhere entered ritz-craft.com as a domain during the
upgrade. DNS is running on the server and all Win2k
clients and XP Pro clients DNS entries point to our main
server 192.168.100.2 in order to join the domain, etc.
All other clients point to our ISP for internet access as
far as DNS 216.169...... etc. After the Win2k and XP
clients join the domain, I can change their DNS entries to
point to the ISP and the web site works. But any Win2k
clients and XP clients that have their DNS entries
pointing to 192.168.100.2 can not view that web site and
that web site only. My computer (network admin) needs the
local DNS to perform admin functions. I went to the DNS
server and added a new host in the Forward Lookup Zone and
named it www and entered the IP Address of our web site
(216.214.52.237) and it said it added successfully but I
still can't view our web site from my PC.
Thanks again.
Keith

Just want to add Kevin, that the poster is putting in their internal DNS to
join, then changes it back to their ISP DNS. I thought you would catch that.

I would like to point out that this is extrememly undesirable. Many other
things *will* occur due to this in respect to domain communication, LDAP,
etc. My suggestions and recommendation are to ONLY use your internal DNS for
all your clients and DCs at all times and configure a forwarder in your DNS
to point to the ISP's for efficient Internet resolution. This is the
consensus of everyone here and the Microsoft enginneers to ensure a smooth
running efficient AD infrastructure. If the forwarding option is grayed out,
delete the Root zone under your forward lookup zone. If not sure how, this
article will show you how to do both of these steps:
http://support.microsoft.com/?id=300202

Here's more info on AD and it's DNS requirements:
http://support.microsoft.com/?id=291382

Hope that helps.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory