To redirect my naked/bare domain to my www domain which is hosted at Heroku, I am using the GoDaddy forwarding feature as mentioned in other posts (Forward to www.mydomain.com, 301 (Perm) redirect, Forward only):
Also the domain details screen is set: Cname (Alias), host: www points to myapp.heroku.com.
While this mostly works, when I visit "mydomain.com" with OSX Chrome, I momentarily see the gray "This webpage is not available" screen before the redirection occurs. Sometimes the delay may even be a few seconds -- long enough that a user might navigate elsewhere before it occurs. (On Safari it works fine).
Is this to be expected with the approach I'm using, and can it be avoided?
220.127.116.11 is GoDaddy. So @ (bare) points at GoDaddy, which resolves it to www, then www is resolved using the CName record to some Heroku IP address. Therefore @ takes an extra roundtrip. Additionally, there's a single GoDaddy IP whereas Heroku has many IPs all over the world, presumably providing a faster response that area.
Seems like if the bare domain could have a CName like record we'd be set, but there are probably good reasons why it can't, such as that other things are going on here as well like email handling.