DNS at FQ and Google Apps setup

[nargonne]

I like letting FQ manage the DNS for my sites mainly so mysql.example.com mappings always work if for some reason ip addresses change internally.

But the problem is with setting up Google Apps where I need mail.example.com, docs, calendar, etc In this case, I manage the DNS through godaddy.com and use IP address for the mysql server when it's needed in my scripts and Drupal setup.

My concern is if for some reason the IP address on a mysql server changes or database must be moved to another server then all my sites may be impacted and I'll have to manually go through and make the changes in DNS.

Is this the right approach or is there a better option?

[Bob]

I have two domains that I manage the DNS in the same manner however I set a mysql.domain.com A Record in GoDaddy's management panel.

This way I use mysql.domain.com in my scripts and if the MySQL server changes, or IP, I only need to make one single change in my Domain Manager at GoDaddy.

-Bob

[nargonne]

Ok, that's kind of what I do and guess will keep on with. Though it would suck if a mysql server changes because I'd have to fix about 20 sites and that's a lot of work when clients see their sites down.

It would be terrific if FQ had a service option for account owners to config their DNS for Google Apps or even simply a pre-configured Google Apps setup radio button in the CNC mail setup.

[garyd]

I am trying to do this also, but would like to confirm some details before I try anything, primarily b/c I don't understand email set up very well. In fact, my site has been hosted here at FQ since 2003 and I used email for about 2 months and then stopped b/c it seemed like it was a lot to manage.

Here's my set up (just for information)

ditschfitness.com is my main (original) domain , endurancebasecamp.com is a IRO for that domain. ditschfitness is hosted at dotster and endurancebasecamp is hosted at godaddy

I want the site to still run as is but run email through good apps. The email addresses that I'm hoping to use would be:

yyy at endurancebasecamp.com
zzz at endurancebasecamp.com
etc

Here's the tutorial that I'm looking at to get started :

http://blog.ashfame.com/2009/05/google-apps-for-domains-emails/

And here's the information I found on FQ on MX Records :

http://service.futurequest.net/index.php?_a=knowledgebase&_j=questiondetails&_i=73

Are there other things I need to think about prior to trying to set this up. I'm not worried about losing any email as I've never used it before and don't have anything here, but I really don't want my site to stop working or create problems for it.

Thanks for your help and sorry this probably requires a lot of step by step assistance.

[Bob]

Gary,

Currently endurancebasecamp.com uses the FutureQuest Name Servers and in that case you could just Order a MX record change pointing the MX record to the MX servers Google Indicates when you setup their Domain Email hosting.

Note that the Article you linked to matches what I have set for one domain for the Google MX host names however I believe that when you setup Google to handle your mail they will provide you with the MX servers and you would want to be sure and use the ones they indicate if they happen to be different.

Alternatively as endurancebasecamp.com is Registered through GoDaddy you can use their Total DNS Control and manage your own DNS and if you take that avenue you would want to be sure to enter the IP address Assigned for endurancebasecamp.com for your A Host records.

You can determine the IP address from your CNC, or digging the FutureQuest Name Servers as noted here:
http://Service.FutureQuest.net/kb17

-Bob

[garyd]

Thanks Bob -

1. Is there any advantage long term to managing the DNS myself at GoDaddy versus just ordering the MX record change and allowing FQ to do it? The only thing I can think of is that if I'd change hosts at some point, but that doesn't seem likely at this point.

2. Are there any drawbacks? Just wondering what the time / knowledge commitment might be (which is a major reason I didn't do email in the first place)

[Bob]

The one advantage I could see would be that if you manage your own DNS you could quickly switch your settings at anytime.

Say for instance you wanted to experiment with another mail provider or wanted to split your domain, have domain.tld point to FutureQuest and www.domain.tld point elsewhere.

Managing your own DNS you could make those changes on your schedule and switch them back quickly if the result was not what you wanted or the provider had issues...

-Bob

[garyd]

Gary,
Alternatively as endurancebasecamp.com is Registered through GoDaddy you can use their Total DNS Control and manage your own DNS and if you take that avenue you would want to be sure to enter the IP address Assigned for endurancebasecamp.com for your A Host records.

-Bob

Before I make this move, is there anything that I need to consider regarding endurancebasecamp being an IRO? If I just use the IP Address for ditschfitness on the server info page, I'm assuming it will just direct endurancebasecamp to that address and thus both will be still pointing there?

(sorry for asking about the same question, just want to be sure prior to changes .. as it works well now, but do want email - thanks)

[Bob]

Gary,

Pointing the A records to the IP address would be the correct setting and the IR would be unaffected.

If you do a dig for the A record for your main domain and your IR you will see they are pointed to the same IP address.

-Bob

[Terra]

My concern is if for some reason the IP address on a mysql server changes or database must be moved to another server then all my sites may be impacted and I'll have to manually go through and make the changes in DNS.
We have brainstormed this issue today, and we believe we will have a workable solution soon...

Stay tuned as we are working out implementation details... ;)

[Terra]

We interrupt this broadcast in order to bring you an important message:
http://www.aota.net/forums/showthread.php?t=25515

We now return you to your regularly scheduled programming already in progress... :)