Windows Server - How to resolve my domain URL without WWW?

Asked By Nutzer on 29-Feb-08 11:36 AM
All,

We own a domain mycompnay.com, it is also our AD domain name.  We have a
website URL www.mycompany.com.  I added added a 'www' 'A Name' to my
internal Windows DNS so my internal users can hit www.mycompany.com.  Now, I
would like to know how I can resolve http://mycompany.com without the 'www'.
As of right now, people in my network cannot resolve the URL if they hit
http://mycompany.com.
Also, our website is externally hosted.

Hope this makes sense.

Thanks!




gehenna.engin replied on 01-Mar-08 04:11 AM
, I

tp://mycompany.com.

You'll want to add a new A entry to your mycompany.com zone.  Leave
the Host field blank and add the IP address of your server.  When you
click ok, you should see the A entry in the forward lookup zone with
the name of (same as parent folder).
Nutzer replied on 29-Feb-08 03:29 PM
Thanks, but there is a slight problem.  My AD name is the same as my domain.
So as of right now I have 3 A records with Host blank(same as parent) and
IP's of my DC's.  So I tried adding another A record with no Host and IP's
pointing to my external site but when I tried hitting it, it goes back
internally to one of my DC's.

Any other ideas?




You'll want to add a new A entry to your mycompany.com zone.  Leave
the Host field blank and add the IP address of your server.  When you
click ok, you should see the A entry in the forward lookup zone with
the name of (same as parent folder).
gehenna.engin replied on 01-Mar-08 04:11 AM
That's the only method I'm aware of.  Normally, I believe it's not
best practice to make your AD domain the same as your external domain
name.  If anything you should make your AD domain a sub-domain of your
external domain or make it completely different.

ain.
's
I
.
Lanwench [MVP - Exchange] replied on 29-Feb-08 06:27 PM
Since you've got the same AD domain name as your public/internet domain
name, you can't do this without breaking AD, as far as I'm aware. Train
users to type www or add a favorite/bookmark to their web browsers. This is
the most minor of inconveniences.

In general, it's better to avoid this configuration if you can - e.g., use
internal.mycompany.com, or mycompany.local, for AD, and leave mycompany.com
on the outside. I don't think it's worth a domain rename (even if that's a
possibility on your network/versions/etc - but just bear that in mind for
future reference.
Kevin D. Goodknecht Sr. [MVP] replied on 04-Mar-08 02:00 PM
Read inline please.

Nutzer <nutzer@ms.com> typed:
Configure a website on all domain controllers in the domain for
http://mycompany.com, then on the web site properties sheet, select the Home
Directory tab, select "A redirection to a URL" type in
http://www.mycompany.com to the field that opens.


This won't work if the domain is the same as the AD domain, the AD domain
name must only resolve to IP addresses of Domain controllers that have file
sharing enabled on them. This is for the \\company.com\SYSVOL and
\\company.com\NETLOGON DFS shares, where GPOs and logon scripts are stored.
Changing this behavior will cause members to look to the Web server for
logon scripts and GPOs.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
Blake replied on 18-Apr-08 12:06 PM
split-brain DNS

Blake