DNS unable to resolve WEBSITE of same AD network name

  • Thread starter Thread starter Rusty
  • Start date Start date
R

Rusty

I am new to Active Dir. and DNS, so please tolerate what I
believe should be a simple question.

I am running a windows 2000 AD network. My website is
hosted by another company outside of my network. The
website and network have the same domain name (for this
question, we'll call them both mydomain.com).

If I try to view my website on a computer inside my
network, DNS is unabe to resolve the address. Typing the
IP address works just fine. The DNS server is able to
resolve all other queries with out any problems.

I think I simply need to create forward lookup zones on my
DNS server that point www, SMTP, and POP traffic to the
correct IP. Is that correct? If so, can you point me to
some documentation on how to correctly do that?

Thanks in advance,

Rusty
 
if your AD is called mydomain.com, then it's time for you to start telling
your users to ALWAYS use WWW.mydomain.com whenever they want to access your
website.

Now, what you need to do is to create an A (host) record called www in your
mydomain.com zone. For the IP address, specify the IP address that your web
host provider is using externally.

If you want to ask whether it's possible to NOT use the www part for the
URL, forget it.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
In (e-mail address removed) <[email protected]>
wrote their comments
Then Kevin replied below:
I followed the steps found on this MS support article:
http://support.microsoft.com/default.aspx?scid=kb;EN-
US;308201

When I click 'Add Host' I get this error:

Warning: the associated pointer (PTR) record cannot be
created, probably because the referenced revers lookup
zone could not be found.

any ideas?
Click to expand...

Do not select "create PTR record"

Even if you had a reverse lookup zone for the public IP it would not be
authoritative and could cause problems if you have a mail server.
 
Back
Top