1530297 - Update DNS entries for srihash.org

Status: RESOLVED FIXED

(Infrastructure & Operations :: DNS and Domain Registration, task)

Description

[Frederik Braun [:freddy]]

It seems the DNS entries for srihash.org are misaligned.

Please set up as follows:

srihash.org      ALIAS or ANAME   aquatic-muskmelon-z6a3o64mw6wk7v9u47r0pxkz.herokudns.com
www.srihash.org  CNAME            octagonal-bitterroot-5voyy4z5vfx344u7b2ws622e.herokudns.com

Comment 1

[Rob Tucker [:rtucker]]

I've set up the DNS as requested.

I would have expected:
www.srihash.org CNAME srihash.org though?

Please reopen if there are any changes that need made.

Comment 2

[Frederik Braun [:freddy]]

I think we wanted redirection, so one is the (enforced) canonical name and redirects to the other. Thanks Rob!

Comment 3

[Frederik Braun [:freddy]]

The name srihash.org does not resolve. Here's what heroku tells me should be the DNS records (same as above, it seems):

srihash.org ALIAS or ANAME aquatic-muskmelon-z6a3o64mw6wk7v9u47r0pxkz.herokudns.com
www.srihash.org CNAME octagonal-bitterroot-5voyy4z5vfx344u7b2ws622e.herokudns.com

Comment 4

[Rob Tucker [:rtucker]]

Seems as though akamai isn't allowing or doesn't know what to do with an apex alias. Will dig further.

Comment 5

[Frederik Braun [:freddy]]

It seems to me that this is non-standard though supported by some specific providers according to https://serverfault.com/questions/613829/why-cant-a-cname-record-be-used-at-the-apex-aka-root-of-a-domain

Comment 6

[Rob Tucker [:rtucker]]

You cannot do a CNAME as an apex per the RFC, which is why the existence of ALIAS records. Akamai doesn't seem to support alias records however.

Digging deeper to see if there is a solution.

Comment 7

[Rob Tucker [:rtucker]]

SERIAL in the SOA matches as is expected.

My guess is that akamai isn't going to support this.

Few options.

1. Treat the root record as an A.
2. Delegate DNS for this to somewhere else. Does heroku host DNS? I know that route53 supports this kind of use case.
3. Open a ticket with akamai, this is unlikely to get us anywhere.

Option 2 is probably the best technical solution.

Comment 8

[Frederik Braun [:freddy]]

Heroku does not support DNS, it seems.
I'm not enthused about the idea of maintaining DNS for this side-project myself.
Is this something you could help me out with?
Happy to have DNS covered by some other server than currently - whoever it is.

I have used free DNS hosting from freedns.afraid.org for fun-projects in my not-so-recent past, but quite doubtful whether this is a good idea. Do we have other services at Mozilla we can use here?

Comment 9

[Rob Tucker [:rtucker]]

There's nothing that I can help you with based on this setup due to Akamai.

I'm route53 can do this, however I'd need to delegate the zone there and someone would have to manage it.

If you could get Address records for the apex that would allow this to work on Mozilla infra.

Comment 10

[Frederik Braun [:freddy]]

OK, I've been thinking and I came to the conclusion that it's easiest to host the apex record someplace else than heroku and just issue a permanent redirect (HTTP 301).

Rob, can you point the dns for the apex domain like so?

A -> 185.26.156.47
AAAA -> 2a00:d0c0:200:0:b9:1a:9c2f:27

The www subdomain should be kept as is.

Thank you!

Comment 11

[Rob Tucker [:rtucker]]

I deleted the ALIAS records and replaced them with the A and AAAA as requested.

Let me know what else I can do here and if this can be closed out.

Thanks!

Comment 12

[Frederik Braun [:freddy]]

Thanks for the quick help, Rob! :)
Glad I got this figured out eventually.