I was going to post this as a comment against DNS: Forward domain to another host, but I don't seem able to do that.
I'm in a similar situation. I have a DNS registered/managed by enom, except with
the slight twist that
the domain was originally registered with enom through a Google Apps account creation.
The domain currently supports a Google Apps site/account. I now want to direct
the bare primary domain and www entries to a hosting provider for
the website component, but leave
the Google Apps setup intact for its services such as calendar, mail etc. For now, I'm leaving
the domain managed by enom.
Also note that when I registered my account with
the hosting provider, I gave
the same domain name as
the existing domain (e.g. example.com), so at their end I'm working with
the same domain name in cpanel, etc.
In my case,
the existing enom DNS entries don't have an A record for
the www.example.com, or
the bare example.com domain. Instead, there are 4 x @ records with
the Google Apps IP Address, 2 x TXT records with what I assume are Google Apps site verification strings/tokens, and a bunch of CNAME records for
the various features of Google Apps (mail, calendar, docs, sites, etc).
So, my questions:
How do I point
the www.example.com and example.com DNS entries at enom to my web site hosting provider, while leaving
the domain managed by enom, and
the Google Apps services working as they are now (with
the obvious exception of Google Sites)?
How do I setup
the example.com mail-related DNS records (MX, etc) at
the web site hosting provider, so that outbound email to
[email protected] gets correctly sent to
the google apps mail account, and doesn't get trapped inside
the pseudo domain within
the hosting providers servers?
