Web Site entry

[Jeff]

This is probably easy but I am missing something. To access our
website you must type www.xyz.com. A request was put in to allow
people to simply type xyz.com and get to the site as well. How do I
set this up in DNS? Thanks.

 

[Deji Akomolafe]

you right-click on the xyz.com zone, create a new A record, don't type
anything for the name, just enter the IP address of your webserver/website.

Done.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon

 

[Kevin D. Goodknecht [MVP]]

In Jeff <[email protected]> posted a question
Then Kevin replied below:
: This is probably easy but I am missing something. To access our
: website you must type www.xyz.com. A request was put in to allow
: people to simply type xyz.com and get to the site as well. How do I
: set this up in DNS? Thanks.
:
:
:
:
:
:

This requires a blank host with the IP of the website. There's a but to
this.
BUT, if xyz.com is your Active Directory domain name, your DCs will create a
blank record for each IP address on the machine. This blank record is
required and must point to the IP on the interface that has File sharing
bound to it. This is how Group policies are deployed to all machines in your
domain, through \\xyz.com\SYSVOL\xyz.com\policies Therefore this record must
stay in place and must point to your internal interface that has file
sharing.
The best workaround I have found is to run IIS on your DCs with a website
configured to listen on this same address. then on the Home Directory tab of
the website in IIS use website redirection to http://www.xyz.com/. This will
allow you to type in xyz.com in your browser and have IIS on the DC redirect
you to your public website.
You could just ask that everyone use www.xyz.com instead.

 

[Jeff]

you right-click on the xyz.com zone, create a new A record, don't type
anything for the name, just enter the IP address of your webserver/website.

Done.

Ok. I had tried this previously and now tried it again. It will not
resolve. Let me give you a little more info as it might help. Our
web site domain name and our AD domain name are different. Our DNS
server is not public. We could not resolve the external IP address
from the inside so I had to add a zone to our DNS server pointing to
the inside address. Now, the www works fine. However, I cannot get
the other one to work. Is that because of the way we are setup?

 

[Jeff Cochran]

Ok. I had tried this previously and now tried it again. It will not
resolve. Let me give you a little more info as it might help. Our
web site domain name and our AD domain name are different. Our DNS
server is not public. We could not resolve the external IP address
from the inside so I had to add a zone to our DNS server pointing to
the inside address. Now, the www works fine. However, I cannot get
the other one to work. Is that because of the way we are setup?

No. You *need* a blank host record pointing to the IP of your web
server in the domain. If your web site domain is configured as an AD
domain, you may need to delete the root account "." to do this.

Jeff

 

[Kevin D. Goodknecht [MVP]]

In Jeff <[email protected]> posted a question
Then Kevin replied below:
: On Tue, 20 Jan 2004 15:25:56 -0800, "Deji Akomolafe"
:
:: you right-click on the xyz.com zone, create a new A record, don't
:: type anything for the name, just enter the IP address of your
:: webserver/website.
::
:: Done.
:
: Ok. I had tried this previously and now tried it again. It will not
: resolve. Let me give you a little more info as it might help. Our
: web site domain name and our AD domain name are different. Our DNS
: server is not public. We could not resolve the external IP address
: from the inside so I had to add a zone to our DNS server pointing to
: the inside address. Now, the www works fine. However, I cannot get
: the other one to work. Is that because of the way we are setup?
:
Since this is not your AD domain and apparently you host the website
locally, in the xyz.com foward lookup zone add a blank record with your
webserver's address (the same address as the www record) If you use host
headers you will also need a host header for xyz.com.
You may need to run ipconfig /flushdns because negative answers are cached,
too.