Your DNS idea is fine. You can point your DNS to whatever you like - the key to having your WWW site show up properly is the Virtual Host setting in Apache or the Host Header settings in IIS. It's extraordinarily simple to configure, and is likely something your web host can configure if asked. They just need to setup a virtual host / host header so that when a request comes in for 'emergency.floridadistillers.com' it goes to your data.
So. what exactly do you folks distill anyhow? :-) Cheers, SJ _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sharyn Schmidt Sent: Tuesday, August 07, 2007 12:33 PM To: [email protected] Subject: [IMail Forum] WAY OT: For the DNS Gurus We are using a hosting company. Our developer is putting together a website that will be accessed by handheld devices. We wanted to call the website <http://emergency.floridadistillers.com> http://emergency.floridadistillers.com to resolve to 64.79.167.6, which is the address of the box that the webhosting company gave us. The hosting company gave us one of their URL's to use: http:\\floridadist.web117.discountasp.net <http://floridadist.web117.discountasp.net> The developer informs me that the only way this website is going to work is if the URL that was provided by the hosting company is used, however, my boss wants to use the emergency.floridadisillers.com URL. I run my own primary nameserver here for floridadistillers.com. Originally, my thought was to just create an A record for emergency and point it to 64.79.167.6. Now I am being told that somehow I have to point emergency to floridadist.web117.discountasp.net. Is there a way to do this in my DNS? I thought maybe the "alias" record would work for this (I'm using MS DNS on a win2k server machine) but it's not resolving. Suggestions? Thanks, Sharyn
