No. That's not valid. It looks like the site is on a shared server so the simple www record will suffice since the provider is likely using host headers to present the correct content. Just put in an A record with the ip, or a CNAME to site444.whatever.com and you should be good to go. Let us know if it doesn't work.
From: James Kerr [mailto:[email protected]] Sent: Friday, August 14, 2009 11:12 AM To: NT System Admin Issues Subject: Re: DNS change- what did I do wrong? Can I setup an alias for www in this format "site444.website.com/website" ? ----- Original Message ----- From: Richard Stovall <mailto:[email protected]> To: NT System Admin Issues <mailto:[email protected]> Sent: Friday, August 14, 2009 11:04 AM Subject: RE: DNS change- what did I do wrong? You need a record for www pointing to the external provider. E.g. an A record with the static IP at your provider. From: James Kerr [mailto:[email protected]] Sent: Friday, August 14, 2009 11:02 AM To: NT System Admin Issues Subject: DNS change- what did I do wrong? In order to fix some issues with Exchange I needed to create an alias mail.domainname.org which is our external MX record. Basically I want anything internal that goes to mail.domainname.org to go to our Exchange server and its working but when I try to go to www.domainname.org with a browser I can't connect to the site. This is what I did in DNS. I created a new forward lookup zone (without AD) called domainname.org and created an alias called mail. This works but what do I need to do to be able to access the website which isn't hosted with us? Maybe I just went about this all wrong from the get go? James ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
