Yes, those MX records are our corporate ones for Heroku. They do no  
have anything to do with your apps.

Best,

MOrten

On Apr 13, 2009, at 4:11 PM, Brian Armstrong wrote:

>
> Interesting, I was able to set it up as a root level domain with
> GoDaddy.com
>
> buyersvote.com pointing to heroku.com
>
> @Keenan, what did you have to do with the MX records?  I am using
> Google Apps to handle the email and I assume I should setup something
> like this?
> http://articles.slicehost.com/2007/10/25/creating-mx-records-for-google-apps
>
> It looks like Heroku already has these MX records setup for Google
> Apps:
> Macintosh:BuyersVote barmstrong$ host buyersvote.com
> buyersvote.com is an alias for heroku.com.
> heroku.com has address 75.101.163.44
> heroku.com has address 75.101.145.87
> heroku.com mail is handled by 5 alt2.aspmx.l.google.com.
> heroku.com mail is handled by 10 aspmx2.googlemail.com.
> heroku.com mail is handled by 10 aspmx3.googlemail.com.
> heroku.com mail is handled by 10 aspmx4.googlemail.com.
> heroku.com mail is handled by 10 aspmx5.googlemail.com.
> heroku.com mail is handled by 1 aspmx.l.google.com.
> heroku.com mail is handled by 5 alt1.aspmx.l.google.com.
>
> But I'm guessing I should set it up with my own domain on GoDaddy to
> avoid potential spam issues?  (where the email from address says
> buyersvote.com but the reverse dns says heroku?)  I don't quite
> understand how this works, just guessing...if someone has more info
> please let me know.
>
> Thanks!
> Brian
>
> On Apr 12, 7:20 pm, Matthew Winter <[email protected]> wrote:
>> Hi,
>>
>> I read an blog post recently on the subject of comparing hosted DNS
>> providers:
>>
>>        http://dns.learnhub.com/lesson/11620-how-to-compare-hosted-dns-provid 
>> ...
>>
>> The article got me thinking about the current use of cname at Heroku,
>> and how you would need to incur double name resolution costs.
>>
>> Take your domain "sonic.net".
>>
>> A user enters "www.sonic.net" into their browser, the browser then
>> makes a requests from your DNS to be passed back the name
>> "heroku.com", a second request would then need to be made to the
>> Heroku DNS, to obtain the IP address.
>>
>> So using the figures given in that website, the average response for
>> the DNS request was 113ms, meaning for accessing an application
>> deployed on Heroku, you would need on average 226ms, with the worst
>> time being 760ms.
>>
>> So the user would have to wait up to 3/4 of a second before the
>> browser even makes the request for the webpage.
>>
>> Maybe Heroku could offer DNS services, as a paid for option. So
>> removing the need for 2 requests, and therefore cutting the response
>> times even further. As long as we have some way of modifying the MX
>> records I am sure most people would be happy to pay for the service,
>> once there sites take off.
>>
>> Regards
>> Matthew Winter
>>
>> On 13/04/2009, at 2:24 AM, shenry wrote:
>>
>>
>>
>>> I wasn't able to get Sonic.net to allow the root-level domain to  
>>> point
>>> to either the www subdomain or heroku.com (in both cases it said it
>>> was an invalid IP.)
>>
>>> I had to make an .htaccess file that redirects root-level domain
>>> requests to the www subdomain, which then goes to heroku.com.... I'm
>>> sure this is hurting performance but I'm not sure if there is  
>>> another
>>> way to get sonic.net to play nice.
>>
>>> Any ideas?
>>
>>> Stu
>>
>>> On Apr 12, 7:27 am, Keenan Brock <[email protected]> wrote:
>>>> Having a primary domain as a cname sometimes messes with mail mx
>>>> records.
>>
>>>> Sometimes the DNS host can't figure it out. Godaddy gave me all  
>>>> sorts
>>>> of issues setting up the cname.
>>
>>>> But all in all, it works in the end. Other DNS hosts are easier.
>>
>>>> Best of luck
>>
>>>> --Keenan
>>
>>>> On Apr 11, 2009, at 9:06 PM, Brian Armstrong <[email protected]>
>>>> wrote:
>>
>>>>> http://docs.heroku.com/custom-domains
>>
>>>>> In the docs it says "or it could be the root-level domain,
>>>>> mydomain.com, though this last one has some caveats described
>>>>> below".
>>
>>>>> I didn't see anything describing below, what should we watch out
>>>>> for?
>>
>>>>> Thanks!
>>>>> Brian
>>
>>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to