That's just resolver output - the DNS records are for heroku, but dig will attempt to resolve CNAMES to a final IP address.
So ignore the heroku A records - www.myles.id.au. 6558 IN CNAME myles.heroku.com. is the one to look at. And it doesn't look like WTFdns does redirects. On 22/06/2009, at 1:37 AM, Jean-Marie Schweizer wrote: > > Hey Miles, > >> myles.id.au. 6877 IN A 69.72.142.98 >> myles.id.au. 6877 IN A 216.98.141.250 > > That's definitely a way to go. I got to find out if wtfdns.com > offers that. > >> www.myles.id.au. 6558 IN CNAME myles.heroku.com. >> myles.heroku.com. 10158 IN CNAME heroku.com. >> heroku.com. 4185 IN A 75.101.163.44 >> heroku.com. 4185 IN A 75.101.145.87 > > Would it still work if I used > > www CNAME proxy.heroku.com. > mail CNAME ghs.google.com. > ... MX records ... > > I'm just a bit confused about your setup since it shows A records for > Heroku, which is exactly what they don't want you to do. > > Anyway, thanks for the tip. I was wondering if a DNS service would > offer automatic redirection like you obviously have at zonenet.com. > > - JM > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
