1093285 - firefox10.org dns

Status: RESOLVED FIXED

(Infrastructure & Operations :: SSL Certificates, task)

Description

[tad]

Please point firefox10.org delegation to
ns-463.awsdns-57.com
ns-664.awsdns-19.net
ns-1323.awsdns-37.org
ns-1652.awsdns-14.co.uk

Might need approval for this first, so needinfoing cmore

Pretty high priorityy, see blocked bug for info. 10th anniversary

Comment 1

[Chris Turra [:cturra]]

complete.

 $ whois firefox10.org | grep "Name Server:N"
 Name Server:NS-1323.AWSDNS-37.ORG
 Name Server:NS-1652.AWSDNS-14.CO.UK
 Name Server:NS-664.AWSDNS-19.NET
 Name Server:NS-463.AWSDNS-57.COM

Comment 2

[Jessica Osorio [:josorio]]

Hey folks! 

In SF the page is down :( we get redirected to a Firefox download page:
http://awesomescreenshot.com/00e3sbez72

Chris any insights? 

What's going on? :(

Comment 3

[Chris More [:cmore]]

(In reply to Jessica Osorio from comment #2)
> Hey folks! 
> 
> In SF the page is down :( we get redirected to a Firefox download page:
> http://awesomescreenshot.com/00e3sbez72
> 
> Chris any insights? 
> 
> What's going on? :(

That's probably because DNS doesn't get updated immediately and each office probably has a cached DNS entry that says that firefox10.org really points to www.mozilla.org/firefox, which is why you get the download page. It should expire in the next day or so. 

Cturra can probably confirm the DNS expiration and when all clients should be up to date.

Comment 4

[tad]

yep, chris can probably confirm this.

sounds like dns propagation

Comment 5

[Shyam Mani [:fox2mike]]

(In reply to Jessica Osorio from comment #2)
> Hey folks! 
> 
> In SF the page is down :( we get redirected to a Firefox download page:
> http://awesomescreenshot.com/00e3sbez72
> 
> Chris any insights? 
> 
> What's going on? :(

I fixed this yesterday. The cause of this issue was because we had firefox10.org pointing to Mozilla nameservers (initially) and had a redirect in place for the domain. When we changed the authoritative nameservers on this bug, we should have also deleted our internal zone file for this domain, which wasn't done. Therefore, Mozilla offices and other places using our DNS were still seeing the redirect in place, while the rest of the world was hitting AWS. 

I deleted the zone file and Chris wiped out the redirect bits. Mary confirmed it was working last evening, so this should be all good.

Comment 6

[Jessica Osorio [:josorio]]

Hey guys! 

What's up with pushing the GA tracking to prod? It's been a day and we need to get this pushed asap! 

What's the ETA on this?

Please get back to us as soon as possible.

Thank you!

Comment 7

[Chris Turra [:cturra]]

Jessica - this should be a push bug for community IT. i would recommend tracking that work in a separate bug for clarify.

Comment 8

[tad]

https://bugzilla.mozilla.org/show_bug.cgi?id=1084618 Jessica

:)