DNS question

I have about 75 domains that a client wants to point to one single domain. Is there an easy way (using M$ DNS Server) to configure all of these domains to point to one domain w/o a separate entry for each? TIA, Che

You want all the domains to redirect to a single domain?  I'm not sure how to do it in IIS, but if you are on a private IIS install, you could set the default website to redirect to the correct domain, and then set the domain's web site separately. --Ben Doom Che Vilnonis wrote: ----- Excess quoted text cut - see Original Post for more -----

This isn't an IIS question, but a DNS server question. Basically, I don't want to create 75 new "zones" on the DNS Server. Dos this make more sense? You want all the domains to redirect to a single domain?  I'm not sure how to do it in IIS, but if you are on a private IIS install, you could set the default website to redirect to the correct domain, and then set the domain's web site separately. --Ben Doom Che Vilnonis wrote: > I have about 75 domains that a client wants to point to one single domain. > Is there an easy way (using M$ DNS Server) to configure all of these > domains to point to one domain w/o a separate entry for each? > > TIA, Che

Under linux, it'd be pretty easy to do this without adding more than 1 zone file. On Jan 7, 2008 11:40 AM, Che Vilnonis <chevy@asitv.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

Use the Cname attribute in the DNS record. If server 2003is the same as 2000, you can open up the DNS file created by Windows and add the domains it manually. I am not sure where it is located; it has been years since I last did this. You can look at the how Cname is used for the mail server as an example of the syntax. Or google it. Jerry Guido Programmer MGT of America, Inc. jguido@mgtamer.com The information contained in this electronic communication is intended only for the use of the addressee, and may be a confidential communication.  If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, distribution or copying of this transmittal is strictly prohibited. This isn't an IIS question, but a DNS server question. Basically, I don't want to create 75 new "zones" on the DNS Server. Dos this make more sense? You want all the domains to redirect to a single domain?  I'm not sure how to do it in IIS, but if you are on a private IIS install, you could set the default website to redirect to the correct domain, and then set the domain's web site separately. --Ben Doom Che Vilnonis wrote: > I have about 75 domains that a client wants to point to one single domain. > Is there an easy way (using M$ DNS Server) to configure all of these > domains to point to one domain w/o a separate entry for each? > > TIA, Che

So you want to point multiple domains to the same IP, but not necessarily redirect them? I don't know of a way in MS DNS.  I know there is a way in BIND. I've seen an option for MS DNS on 2k3 to store the info in files only, so you may be able to c&p the files, renaming them appropriately to create the new zones. --Ben Doom Che Vilnonis wrote: ----- Excess quoted text cut - see Original Post for more -----

Can anyone comment on the SEO ramifications of pointing mulitple domains at the same site rather than 301 redirecting them? Adrian So you want to point multiple domains to the same IP, but not necessarily redirect them? I don't know of a way in MS DNS.  I know there is a way in BIND. I've seen an option for MS DNS on 2k3 to store the info in files only, so you may be able to c&p the files, renaming them appropriately to create the new zones. --Ben Doom Che Vilnonis wrote: > This isn't an IIS question, but a DNS server question. Basically, I don't > want to create 75 new "zones" on the DNS Server. Dos this make more sense? > > You want all the domains to redirect to a single domain?  I'm not sure how > to do it in IIS, but if you are on a private IIS install, you could set the > default website to redirect to the correct domain, and then set the domain's > web site separately. > > --Ben Doom > > Che Vilnonis wrote: >> I have about 75 domains that a client wants to point to one single domain. ----- Excess quoted text cut - see Original Post for more -----

> Can anyone comment on the SEO ramifications of pointing mulitple domains > at > the same site rather than 301 redirecting them? Hi Adrian, I recently had to deal with some SEO issues - I don't have a good answer for you, but there is a discussion board at Google Groups with folks who could probably answer your question pretty definitively: http://groups.google.com/group/Google_Webmaster_Help-Indexing/topics There were some people on that board who were very helpful when I had some questions. -- Josh

I think "bad" is probably a good summary.  I know Google, for one, punishes multiple sites with the same or substantially similar (ie, different nav, or CSS) content. --Ben Doom Adrian Lynch wrote: ----- Excess quoted text cut - see Original Post for more -----

You are most likely going to end up adding the host records for each. Not only to DNS but in IIS as well. As for DNS, it should be pretty easy and quick to add that many if you use the dnscmd command rather than the GUI. Just type `dnscmd /recordadd /help` on the DNS server to figure out the command options. I'm also pretty sure you can add the host headers to IIS via command line as well. Seems like I saw that somewhere before. I haven't used it though.. I normally just type them in manually but then again I've never added 75 at one time. You could also just open up C:\WINDOWS\system32\inetsrv\metabase.xml and add the hostheaders manually then restart everything. Of course, this isn't as easy as just opening it up, editing it and saving it... you will have to free it up first by killing all processes and services that might be using it before you will be allowed to save it with the same name and location. Just find the block in the file that represents the site in question then add more host headers to the ServerBindings section Example... <IIsWebServer  Location ="/LM/W3SVC/123456789"     AuthFlags="0"     ServerAutoStart="True"     ServerBindings=":80:mydomain1.com             :80:mydomain2.com             :80:mydomain3.com"     ServerComment="TheSiteName"   > If you don't back it up first, well... you deserve any misfortunes that may occur ;-) .:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com

If I understand your question correctly and my very limited understanding of DNS applies, maybe? I think what you want to do is 'CNAME' entries into DNS that I believe basically say, "this DNS string is the same is that other DNS string for which I gave a full 'A' description.  Whether you will need 75 of these CNAME entries may depend on your DNS server, its capability to pattern match and how much these 75 DNS names have in common.

> Basically, I don't want to create 75 new "zones" on the DNS > Server. I think you'll have to create the zones. I suspect this can be scripted relatively easily, though. 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!

> Use the Cname attribute in the DNS record. If server 2003is > the same as 2000, you can open up the DNS file created by > Windows and add the domains it manually. I am not sure where > it is located; it has been years since I last did this. I'm pretty sure you'll need to create the zones first. 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!