Combo DNS & IIS Question

[Matthew]

One of our web developers has created a new website in IIS
(let's just call it widgets.com). The objective is for
our users and outside customers to be able to access this
site by typing in www.widgets.com or widgets.com.

I've already done the following:

- Created a standard primary zone in W2K DNS
- Within IIS, I've added both entries under Multiple
Identities for this Web Site
- Added the alias www to the widgets.com standard primary
zone

After the above actions were perfomed, users can access
the website through www.widgets.com, but not by typing
widgets.com

Just for grins, I added another alias entry to the
Standard Primary Zone and left the alias entry blank.
This appeared to fix accessing the website using
widgets.com. Only problem is that this additional entry
fails to replicate to my other DNS server, in which I have
a Secondard DNS Zone configured.

Is there a way to simplify this so that we don't have to
add both alias entries for each website? Also, why won't
my other DNS server (DC), which holds a Secondary DNS
zone, receive the updated info from the Primary Standard
zone? Thanks.

 

[Kevin D. Goodknecht]

In

One of our web developers has created a new website in IIS
(let's just call it widgets.com). The objective is for
our users and outside customers to be able to access this
site by typing in www.widgets.com or widgets.com.

I've already done the following:

- Created a standard primary zone in W2K DNS
- Within IIS, I've added both entries under Multiple
Identities for this Web Site
- Added the alias www to the widgets.com standard primary
zone

After the above actions were perfomed, users can access
the website through www.widgets.com, but not by typing
widgets.com

Just for grins, I added another alias entry to the
Standard Primary Zone and left the alias entry blank.
This appeared to fix accessing the website using
widgets.com. Only problem is that this additional entry
fails to replicate to my other DNS server, in which I have
a Secondard DNS Zone configured.

Is there a way to simplify this so that we don't have to
add both alias entries for each website? Also, why won't
my other DNS server (DC), which holds a Secondary DNS
zone, receive the updated info from the Primary Standard
zone? Thanks.

You need a blank host pointing to the IP of the website.

 

[Jeff Cochran]

One of our web developers has created a new website in IIS
(let's just call it widgets.com). The objective is for
our users and outside customers to be able to access this
site by typing in www.widgets.com or widgets.com.

I've already done the following:

- Created a standard primary zone in W2K DNS
- Within IIS, I've added both entries under Multiple
Identities for this Web Site
- Added the alias www to the widgets.com standard primary
zone

After the above actions were perfomed, users can access
the website through www.widgets.com, but not by typing
widgets.com

Naturally. You didn't provide an entry in DNS to resolve a blank host
to the web server's IP.

Just for grins, I added another alias entry to the
Standard Primary Zone and left the alias entry blank.
This appeared to fix accessing the website using
widgets.com. Only problem is that this additional entry
fails to replicate to my other DNS server, in which I have
a Secondard DNS Zone configured.

Not an alias, you want an A record. Add a blank host record pointing
to the IP of the web server. Force a replication. Have a beer.

It really is that simple.

Jeff

 

[Michael Johnston [MSFT]]

Additionally, if the record still doesn't replicate over, verify that the zone on the secondary is indeed a standard secondary and that the Standard primary is
configured to allow zone transfers to this secondary. If it's still a no go, verify the serial numbers on both zones. The secondary zone should have the same or
lower serial number. If it's higher, or the same, try incrementing the number by one on the primary and force the zone transfer again.

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.