Easiest way to incorporate an email to work with cloud

[Greek76]

What is the easiest way to set up an email account for cloud? In the past I'd make an email account with godaddy and have to email invision to set it up. Is there another method where I could avoid having to that? 

[Randy Calvert]

Are you talking about email with your domain name itself… you need to have your DNS MX and possibly SPF and DKIM records created.  If IPS is hosting your DNS, they will always need to help set those records for you. 

If you’re talking about email only not based on your domain (iCloud, outlook, etc) you would just setup the SMTP settings in your ACP. 

Or if you pick a totally different domain (say your site is myforum.com), you could create myforum-mail.com and since you control that DNS use that. 

[Greek76]

18 minutes ago, Randy Calvert said:

Are you talking about email with your domain name itself… you need to have your DNS MX and possibly SPF and DKIM records created.  If IPS is hosting your DNS, they will always need to help set those records for you. 

If you’re talking about email only not based on your domain (iCloud, outlook, etc) you would just setup the SMTP settings in your ACP. 

Or if you pick a totally different domain (say your site is myforum.com), you could create myforum-mail.com and since you control that DNS use that. 

Yes I meant the DNS MX. It's such a tedious thing to send he information to the team to setup. The Records have to be in line and in perfect order so they could copy and paste each word and line in sequence. I guess there's no escaping it. Thanks

[Randy Calvert]

1 minute ago, Greek76 said:

Yes I meant the DNS MX. It's such a tedious thing to send he information to the team to setup. The Records have to be in line and in perfect order so they could copy and paste each word and line in sequence. I guess there's no escaping it. Thanks

The reason they host your DNS is because if you have domain.com, most people want www.domain.com and domain.com to show the same content.  (Simply "domain.com" is known as a domain apex.)

When you specify a DNS record for the apex, DNS standards require it be an IP address... called an "A" record.  (This standard was created in the 1980's, so it's pretty old.  There was no such thing as load balancing, etc).  However since IPS uses load balancing, there is no single IP address.  That IP address changes every few minutes depending on availability, server load, etc.  

Subdomains like "www"(.domain.com) can be created with CNAME records which are pointers to other addresses.  So having "www" would automatically get you to the correct load balanced location, while the apex cannot get there.  

There are two ways to solve this:

1) Having a single server out there just issue redirects from domain.com to www.domain.com.  This is not a really good idea because what happens if that single server is down, or attacked, etc.  There is no redundancy, etc.  You could lose your redirector.  

2) If IPS hosts your DNS, they can have their manage it at the same time their load balancer makes an update.  This ensures you don't have a single point of failure sitting out there and is the route most customers take.  This is the route IPS generally suggests by default.

** IF YOU DON'T USE DOMAIN.COM/WWW.DOMAIN.COM and instead use something like forums.domain.com or something.domain.com** you don't need to have IPS host the DNS.  Instead your current DNS host can simply create a CNAME record that points forums.domain.com to the IPS platform.  Since you don't have the apex involved, that is all you need to do and you don't have to worry about anything else.  

Ultimately long term, what would be nice would be if IPS would provide an interface for customers to manage their DNS from the Client Area so they could self-service make changes to things like MX records, or create additional A/CNAME records, etc instead of always needing to open a support request.  While that sort of functionality would be wonderful, it means taking developers away from creating new features or fixing bugs, etc.  So the question becomes how often do people really need to change or add records that it makes sense to automate it versus continuing to do the change manually.  

[Marc Stridgen]

For the way you are set up at present, no. However we can quickly get those set up for you if you send them over