Regarding the additional site we created, I might also add that we are
able to ping it successfully.
Sincerely,
Andrew
Webmaster
Illinois Office of the Comptroller
IllinoisComptroller.com
-Original Message-
From: Peterson, Andrew S. [mailto:[EMAIL PROTECTED]
Sent: Friday, November 18,
Andrew,
Why the new zone? What we do is take an existing zone and add a new A
record. If the zone is mydomain.com I might have.
clients.mydomain.com
dev.mydomain.com
www.mydomain.com
etc... all of them A records.
-Mark
-Original Message-
From: Peterson, Andrew S. [mailto:[EMAIL
I'm doing a win2k3 server like this, with a dozen or so host-header'd
domains, right now. In MS DNS at least, you set up the host entry and
the * entry pointing to the shared IP.
Then in IIS6 you set up the host headers with fully qualified domain,
pointing to port 80. I like to use two host
Hire a Network admin that knows a port from a hole in the ground.
-Original Message-
From: Peterson, Andrew S. [mailto:[EMAIL PROTECTED]
Sent: Friday, November 18, 2005 9:26 AM
To: CF-Talk
Subject: OT: Multiple sites in IIS - Modifying DNS
Hello,
I've created an additional site in
I've created an additional site in IIS 6 on my development
server with a unique Host Header. So there are currently two
sites on that server. Now I've got my brilliant Network admin
trying to that second site to the DNS. Thus far, he has failed
miserably :-). He created a new primary
-Original Message-
From: Peterson, Andrew S. [mailto:[EMAIL PROTECTED]
Sent: Friday, November 18, 2005 11:26 AM
To: CF-Talk
Subject: OT: Multiple sites in IIS - Modifying DNS
Hello,
The bottom line is that he blames me, and I blame him, and we're about
to take it outside, in
There's no need to create a new zone. Zones typically correspond to
domains or subdomains. Assuming that both sites on your server use the
same IP address, your network administrator only needs to create a CNAME
record pointing the new host name to the old one. If the sites use
different IP
: Friday, November 18, 2005 12:19 PM
To: CF-Talk
Subject: RE: Multiple sites in IIS - Modifying DNS
I've created an additional site in IIS 6 on my development
server with a unique Host Header. So there are currently two
sites on that server. Now I've got my brilliant Network admin
trying
[mailto:[EMAIL PROTECTED]
Sent: Friday, November 18, 2005 12:19 PM
To: CF-Talk
Subject: RE: Multiple sites in IIS - Modifying DNS
I've created an additional site in IIS 6 on my development
server with a unique Host Header. So there are currently two
sites on that server. Now I've got my
CNAME records should only be used when aliasing a host that
is not within the same zone, otherwise, use A records.
I'm not a DNS expert, but my understanding is that this is simply incorrect.
There's nothing wrong with using CNAME records to alias hosts within a zone.
Dave Watts, CTO, Fig
CNAME records should only be used when aliasing a host
that is not within the same zone, otherwise, use A
records.
I'm not a DNS expert, but my understanding is that this
is simply incorrect. There's nothing wrong with using
CNAME records to alias hosts within a zone.
You CAN alias
The CNAME record is used less than the A record because
it causes more traffic - more lookups. You can have multiple
A records for the same IP. Personally, I think it's easier
to manage just A records.
The performance difference is pretty inconsequential, especially if both
CNAME and A
-Original Message-
From: Justin D. Scott [mailto:[EMAIL PROTECTED]
Sent: Friday, November 18, 2005 1:46 PM
To: CF-Talk
Subject: RE: Multiple sites in IIS - Modifying DNS
CNAME records should only be used when aliasing a host that
is not within
the same zone, otherwise, use
I don't agree with this because CNAME records pointed
to A records make it easier to change IP addresses
for said A records. One scenario would be 10 A records
For people manually managing zone files, I suppose this could make life
easier. I run my own DNS hosting service that uses variables
You CAN alias records within the same zone, but it's
generally not a good idea because of the extra DNS
lookups required to resolve them. Just because you
can do a think, does not mean you should.
Again, though, this is what CNAME records are for. The extra DNS lookups do
not cause a
-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Friday, November 18, 2005 1:46 PM
To: CF-Talk
Subject: RE: Multiple sites in IIS - Modifying DNS
You CAN alias records within the same zone, but it's
generally not a good idea because of the extra DNS
lookups required to resolve them. Just because
CNAME records make it possible to introduce recursion errors.
The extra lookup is definitely an issue for small data centers
trying to maximize bandwidth and resources. And from a management
standpoint it seems easier to work with 1 less kind of record.
At this point, we're quibbling about
17 matches
Mail list logo
