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-providers-with-data
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
-~----------~----~----~----~------~----~------~--~---
