Enable DNSSEC

[XhmikosR]

No description provided.

[jdorfman]

@XhmikosR for www or cdn?

[XhmikosR]

This is for the whole domain, if I remember correctly.

…

On Jan 9, 2018 9:19 PM, "Justin Dorfman" ***@***.***> wrote: @XhmikosR <https://github.com/xhmikosr> for www or cdn? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#954 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVVtbAW0VOfuaqmGMJHTG5MkWFUDFz5ks5tI7vOgaJpZM4RVOQV> .

[petarpetrovic]

I've escalated the request to the System Engineering team. Will let you know once this is done.

[XhmikosR]

@petarpetrovic: any news?

[petarpetrovic]

@XhmikosR still working with the System Engineering team on getting this enabled. Will ping them again today for an update.

[XhmikosR]

@petarpetrovic: ping

[petarpetrovic]

@XhmikosR this will need to get delayed a little bit due to the migration to the new CDN platform. I'll post more details and ETA as soon as I have it.

[jdorfman]

@XhmikosR I have a call with StackPath tomorrow, when we are ready to move over we will make sure this is applied. The new hostname going forward will be stackpath.bootstrapcdn.com. More on that after the move.

[petarpetrovic]

Due to the current limitations on Route 53's end, DNSSEC cannot be enabled at this time. I will be monitoring the Route 53 feature set and I'll revisit this issue once there are any new developments related to DNSSEC on their end.

[XhmikosR]

@jimaek can you please enable DNSSEC too?

[jimaek]

Honestly I prefer not to. I feel that it's too risky. Using multiple DNS providers would become complicated as well as migrating between different DNS providers, and it adds another point of failure to the system.
I want to keep our systems portable to allow us to move fast in case something happens.