RE: Multiple sites in IIS - Modifying DNS
> 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 something pretty small, but I can only say that none of these things have been problems for me or my clients, while I have seen problems using multiple A records pointing to the same IP address. I don't see how working with one less DNS record type makes any difference, since you still have to know SOA, MX, etc. My preference for using CNAME records for aliases is simply that this is what they're intended for, and as a result they provide (slightly) useful information that multiple A records don't provide. And as for the difference in traffic, I don't think there are more requests and responses when you get back a CNAME that's pointing to an A record - you simply get both answers in a single response. At least, that's what nslookup tells me. Here are some sample grabs from nslookup (I changed the names of the servers to protect the innocent - that's why the length of the first request is shorter, even though the server name is longer): > test_cname.figleaf.com. Server: ns.figleaf.com Address: xxx.xxx.xxx.xxx SendRequest(), len 33 HEADER: opcode = QUERY, id = 4, rcode = NOERROR header flags: query, want recursion questions = 1, answers = 0, authority records = 0, additional = 0 QUESTIONS: test_cname.figleaf.com, type = A, class = IN Got answer (72 bytes): HEADER: opcode = QUERY, id = 4, rcode = NOERROR header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 2, authority records = 0, additional = 0 QUESTIONS: test_cname.figleaf.com, type = A, class = IN ANSWERS: -> test_cname.figleaf.com type = CNAME, class = IN, dlen = 11 canonical name = test_a.figleaf.com ttl = 3600 (1 hour) -> test_a.figleaf.com type = A, class = IN, dlen = 4 internet address = xxx.xxx.xxx.xxx ttl = 3600 (1 hour) Name:test_a.figleaf.com Address: xxx.xxx.xxx.xxx Aliases: test_cname.figleaf.com > test_a.figleaf.com. Server: ns.figleaf.com Address: xxx.xxx.xxx.xxx SendRequest(), len 38 HEADER: opcode = QUERY, id = 5, rcode = NOERROR header flags: query, want recursion questions = 1, answers = 0, authority records = 0, additional = 0 QUESTIONS: test_a.figleaf.com, type = A, class = IN Got answer (54 bytes): HEADER: opcode = QUERY, id = 5, rcode = NOERROR header flags: response, auth. answer, want recursion, recursion avail. questions = 1, answers = 1, authority records = 0, additional = 0 QUESTIONS: test_a.figleaf.com, type = A, class = IN ANSWERS: -> test_a.figleaf.com type = A, class = IN, dlen = 4 internet address = xxx.xxx.xxx.xxx ttl = 3600 (1 hour) Name:test_a.figleaf.com Address: xxx.xxx.xxx.xxx You notice the difference? Eighteen bytes. That's it. The answer in either case was small enough to fit within a UDP packet. That's hardly a big amount of traffic, and you'd be better served in most cases just increasing the TTL values so your DNS server is queried less frequently - the DNS server above is an internal server, so it's not a big deal. I'm not saying you're wrong to recommend using A records instead of CNAME records, just that we seem to value different results in this case. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224706 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
Dave, 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. -Mark -Original Message- 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 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 significant amount of traffic, in my experience, even with DNS servers that support high-volume sites. I suspect this may have been more of an issue in the past than it is now, or maybe for DNS servers that support even higher numbers of queries it is still true. However, using multiple A records for a single IP address can introduce other problems, and I prefer the set of problems you may get by using CNAME records to the set of problems that you may get by using A records for aliasing. For example, if you're using the Microsoft DNS server - which, being integral to AD and Windows Networking, many people are - you can easily screw up your PTR records, as each time you add an A record it will, by default, rewrite the PTR record to point to the new host name. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224702 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
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 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 significant amount of traffic, in my experience, even with DNS servers that support high-volume sites. I suspect this may have been more of an issue in the past than it is now, or maybe for DNS servers that support even higher numbers of queries it is still true. However, using multiple A records for a single IP address can introduce other problems, and I prefer the set of problems you may get by using CNAME records to the set of problems that you may get by using A records for aliasing. For example, if you're using the Microsoft DNS server - which, being integral to AD and Windows Networking, many people are - you can easily screw up your PTR records, as each time you add an A record it will, by default, rewrite the PTR record to point to the new host name. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224680 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
> 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 for IP addresses and generates the zones, so it isn't an issue for me personally. My reasoning is based on minimizing the number of lookups that need to be done. As a rule I try to avoid them within the same zone for that reason. It's really not a big enough issue to argue about, so to each their own :). -Justin Scott ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224676 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
> -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 A records. > > -Justin Scott 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 in a zone file that all go to the same IP Address on a server that uses host headers. Changing the IP address would necessitate the change of all the A records. If you use one A record, e.g. mydomain.com IN A 192.168.0.10, and 9 CNAMES, e.g. foo.mydomain.com IN CNAME mydomain.com, etc., you make life a lot easier for yourself or whoever is in charge of the DNS. Andy ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224673 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
> 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 records are within the same zone. But more importantly, this is specifically what CNAME records are for, and it tells me clearly which name a PTR record should resolve to - the name specified within the one A record. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224671 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
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 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 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. -Justin Scott ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224670 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
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 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 Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224666 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
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 A records. -Justin Scott > -Original Message- > From: Mark A Kruger [mailto:[EMAIL PROTECTED] > Sent: Friday, November 18, 2005 1:39 PM > To: CF-Talk > Subject: RE: Multiple sites in IIS - Modifying DNS > > Dave, > > 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. > > -Mark > > > -Original Message- > From: Dave Watts [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 brilliant Network admin > > trying to that second site to the DNS. Thus far, he has failed > > miserably :-). He created a "new primary forward lookup zone." > > On the new primary zone, he created "a host A record corresponding > > to the Host Header name," but only the dns server itself is able > > to resolve it, and in that case, not to the second site, but > > rather the development home page itself. > > > > The bottom line is that he blames me, and I blame him, and we're > > about to take it outside, in which case, we'll be looking for a > > new network admin (LOL). We would greatly appreciate any ideas > > on how to resolve this DNS issue. Thanks! > > 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 > addresses, you need to create a new A record pointing the new > host name to > the appropriate IP address. > > In any case, your network administrator needs to learn how > DNS works, since > it's integral to so many things on a network. Unless you're > changing DNS > entries yourself, there's nothing he can really blame you > for, except that > you're making him do his job. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > > Fig Leaf Software provides the highest caliber vendor-authorized > instruction at our training centers in Washington DC, Atlanta, > Chicago, Baltimore, Northern Virginia, or on-site at your location. > Visit http://training.figleaf.com/ for more information! > > > > > ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224662 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
Dave, 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. -Mark -Original Message- From: Dave Watts [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 brilliant Network admin > trying to that second site to the DNS. Thus far, he has failed > miserably :-). He created a "new primary forward lookup zone." > On the new primary zone, he created "a host A record corresponding > to the Host Header name," but only the dns server itself is able > to resolve it, and in that case, not to the second site, but > rather the development home page itself. > > The bottom line is that he blames me, and I blame him, and we're > about to take it outside, in which case, we'll be looking for a > new network admin (LOL). We would greatly appreciate any ideas > on how to resolve this DNS issue. Thanks! 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 addresses, you need to create a new A record pointing the new host name to the appropriate IP address. In any case, your network administrator needs to learn how DNS works, since it's integral to so many things on a network. Unless you're changing DNS entries yourself, there's nothing he can really blame you for, except that you're making him do his job. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224660 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
>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 addresses, you need to create a new A record pointing the new host name to the appropriate IP address. I agree completely. We have a mix of host headers and distinct IPs here. M!ke ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224658 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
> -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 which case, we'll be looking for a new network > admin (LOL). We would greatly appreciate any ideas on how to resolve > this DNS issue. Thanks! Well... honestly your network admin should know this stuff. If you're talking MS DNS CrystalTech has a nice guide for their (amateur) dedicated server users here: http://www.webcontrolcenter.com/Knowledge_Base/frmKB.aspx?KBID=564 I was able to set up all my domains and DNS using it. Jim Davis ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224656 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
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 to that second site to the DNS. Thus far, he has failed > miserably :-). He created a "new primary forward lookup zone." > On the new primary zone, he created "a host A record corresponding > to the Host Header name," but only the dns server itself is able > to resolve it, and in that case, not to the second site, but > rather the development home page itself. > > The bottom line is that he blames me, and I blame him, and we're > about to take it outside, in which case, we'll be looking for a > new network admin (LOL). We would greatly appreciate any ideas > on how to resolve this DNS issue. Thanks! 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 addresses, you need to create a new A record pointing the new host name to the appropriate IP address. In any case, your network administrator needs to learn how DNS works, since it's integral to so many things on a network. Unless you're changing DNS entries yourself, there's nothing he can really blame you for, except that you're making him do his job. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224655 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
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 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 forward lookup zone." On the new primary zone, he created "a host A record corresponding to the Host Header name," but only the dns server itself is able to resolve it, and in that case, not to the second site, but rather the development home page itself. The bottom line is that he blames me, and I blame him, and we're about to take it outside, in which case, we'll be looking for a new network admin (LOL). We would greatly appreciate any ideas on how to resolve this DNS issue. Thanks! Sincerely, Andrew -Original Message- From: Snake [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 11:12 AM To: CF-Talk Subject: RE: Multiple sites in IIS Yes, use different host headers instead of ports. Use a subdomain off your primary domain for your dev server, Russ -Original Message- From: Peterson, Andrew S. [mailto:[EMAIL PROTECTED] Sent: 15 November 2005 15:29 To: CF-Talk Subject: OT: Multiple sites in IIS Hi, We have one development server, and multiple production servers. For each separate server in production, I'm just creating a New Site in IIS on the development server, each using a different port. Is there a better way/best practices approach to keeping these servers separate in the development environment? Thanks in advance. Sincerely, Andrew ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224652 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Multiple sites in IIS - Modifying DNS
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 headers for that: domain.com www.domain.com I use the * host entry to signify 'www and anything else' although I could just put in 'www' too. If you want to add a second site, like service.domain.com then you add a new host in the existing dns record, pointing specifically to "service" in the New Host dialog. Then point the new host to the shared IP. Get yourself back into IIS and make up a new web site whose only host header is service.domain.com And which points to port 80 (or whatever) and thats all there is to it. To do a totally different domain, such as 'foo.com', you set up a completely new DNS record, with the host and * entries pointing to the shared IP. Do the same as above for IIS host headers and you're done. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224651 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
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 PROTECTED] Sent: Friday, November 18, 2005 11:26 AM To: CF-Talk Subject: OT: Multiple sites in IIS - Modifying DNS Hello, 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 forward lookup zone." On the new primary zone, he created "a host A record corresponding to the Host Header name," but only the dns server itself is able to resolve it, and in that case, not to the second site, but rather the development home page itself. The bottom line is that he blames me, and I blame him, and we're about to take it outside, in which case, we'll be looking for a new network admin (LOL). We would greatly appreciate any ideas on how to resolve this DNS issue. Thanks! Sincerely, Andrew -Original Message- From: Snake [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 11:12 AM To: CF-Talk Subject: RE: Multiple sites in IIS Yes, use different host headers instead of ports. Use a subdomain off your primary domain for your dev server, Russ -Original Message- From: Peterson, Andrew S. [mailto:[EMAIL PROTECTED] Sent: 15 November 2005 15:29 To: CF-Talk Subject: OT: Multiple sites in IIS Hi, We have one development server, and multiple production servers. For each separate server in production, I'm just creating a New Site in IIS on the development server, each using a different port. Is there a better way/best practices approach to keeping these servers separate in the development environment? Thanks in advance. Sincerely, Andrew ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224650 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Multiple sites in IIS - Modifying DNS
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, 2005 11:26 AM To: CF-Talk Subject: OT: Multiple sites in IIS - Modifying DNS Hello, 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 forward lookup zone." On the new primary zone, he created "a host A record corresponding to the Host Header name," but only the dns server itself is able to resolve it, and in that case, not to the second site, but rather the development home page itself. The bottom line is that he blames me, and I blame him, and we're about to take it outside, in which case, we'll be looking for a new network admin (LOL). We would greatly appreciate any ideas on how to resolve this DNS issue. Thanks! Sincerely, Andrew -Original Message- From: Snake [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 11:12 AM To: CF-Talk Subject: RE: Multiple sites in IIS Yes, use different host headers instead of ports. Use a subdomain off your primary domain for your dev server, Russ -Original Message- From: Peterson, Andrew S. [mailto:[EMAIL PROTECTED] Sent: 15 November 2005 15:29 To: CF-Talk Subject: OT: Multiple sites in IIS Hi, We have one development server, and multiple production servers. For each separate server in production, I'm just creating a New Site in IIS on the development server, each using a different port. Is there a better way/best practices approach to keeping these servers separate in the development environment? Thanks in advance. Sincerely, Andrew ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224648 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
