At the webhosting company I have the MX record pointing to an A record like its supposed to be. What i'm doing now is all internal DNS stuff.
James ----- Original Message ----- From: Micheal Espinola Jr To: NT System Admin Issues Sent: Friday, August 14, 2009 11:41 AM Subject: Re: DNS change- what did I do wrong? Just in case: MX records should not point to CNAME records (aliases). MX records should point to A records only. Spam filters may see this and penalize and/or block you. Many web sites are servers that virtually serve web site content based on the connecting host header (FQDN that is being used to resolve to the IP address of the server); this is how a single server can host many web sites simultaneously. If the web server is not configured for FQDN you are trying to connect to, it has no host header information in which to virtually serverthe correct content for. So, if I understand this correctly, you need to contact your web host and have them add your new FQDN as an additional host header for your site. -- ME2 On Fri, Aug 14, 2009 at 11:01 AM, James Kerr <[email protected]> wrote: 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/> ~
