Re: Can get to www.abc.com but not abc.com
- From: "Ace Fekay [Microsoft Certified Trainer]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Apr 2009 15:20:07 -0400
In news:E832F93F-3643-443E-81F1-153C46C50271@xxxxxxxxxxxxx,
Lori <Lori@xxxxxxxxxxxxxxxxxxxxxxxxx>, posted the following:
Forgot to mention, this is an INTERNAL problem only. All external
requests resolve correctly with & without www.
Also should mention that in 2 of the scenarios the website domain is
the same as the internal domain. The other 7 web sites are that only
- just web sites.
Lori,
Please read my following blog on this issue.
======================================================================================================
======================================================================================================
AD domain name is the same name internal and external
Or
From inside the office, I can't get to http://domain.com, but can usinghttp://www.domain.com
Is your internal domain name and external domain name the same? If so, it's called a split zone. To allow your internal users to get to your external webserver in such a scenario, simply create a "A" www record and provide the IP address of the external web server. If your ISP uses more than one web servers, such as a server farm, instead of an "A" record, I suggest to create a delegation for 'www' to the public name servers. This can be done by rt-clicking your zone, new delegation, type in www, and provide the SOA of your public domain.
As for getting to the domain with http://domain.com (without the www in front of it), is a little more complex because EACH domain controller registers themselves into DNS with an IP address as:
(same as parent) A x.x.x.x
This record is actually called the LdapIpAddress. Each DC registers one for itself. AD uses that record for a number of things, such as GPOs and DFS. Don't mess with it please.
To get around that, on EACH DC, install IIS. In the default website properties, directory tab, redirect it to www.domain.com.
More info and scenarios:
If the same internal and external name and website is hosted externally:
Simply adding a www host record (NOT and alias) under your internal name and providing the external web server's IP address will be sufficient, but you must always use 'www' in front of it. You can also delegate the www record as explained above. The blank record, http://myweb.com is a little more complex to make it work, as I've stated because the of the LdapIpAddress record that appears as: "(same as parent) A x.x.x.x" is actually a record each DC creates as part of the netlogon SRV registration process. This cannot be changed, however to get around it, you can install IIS on EACH and every domain controller. In the default website properties, configure a redirect to 'www.myweb.com,' and anytime anyone enters http//myweb.com, it will be redirected automatically.
If the same internal and external name and the public website is hosted internally:
Create a www host record giving it the internal private IP address. Install IIS on EACH and every domain controller. In the default website properties, configure a redirect to 'www.myweb.com,' and anytime anyone enters http//myweb.com, it will be redirected automatically.
If different internal and external name and website hosted externally:
Nothing to do. Internet resolution will handle everything. Configure a forwarder for more efficient internet name resolution.
======================================================================================================
Ace
.
- Follow-Ups:
- Re: Can get to www.abc.com but not abc.com
- From: Lori
- Re: Can get to www.abc.com but not abc.com
- References:
- Can get to www.abc.com but not abc.com
- From: Lori
- RE: Can get to www.abc.com but not abc.com
- From: Lori
- Can get to www.abc.com but not abc.com
- Prev by Date: Re: adding device to DNS
- Next by Date: Clients freeze up
- Previous by thread: RE: Can get to www.abc.com but not abc.com
- Next by thread: Re: Can get to www.abc.com but not abc.com
- Index(es):
Relevant Pages
|