Closed Bug 843468 Opened 7 years ago Closed 7 years ago
.mozilla .org is gone
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Build ID: 20130212082553 Steps to reproduce: My two frontier DNS servers (220.127.116.11, 18.104.22.168) do not resolve releases.mozilla.org, but Google's (22.214.171.124) DNS's do. Are you guys up to something?
http://www.frontierhelp.com/faq.cfm?qstid=143 says to use: 126.96.36.199 188.8.131.52 and they don't work either
Shouldn't you rather report this to that ISP? Resolving since I doubt this is a Mozilla Issue.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
This seems to be a bigger issue, Mnyromyr and I also have this problem, so at least 3 ISPs fail to resolve the address, likely more.
Ok, confirmed over here too with ISP DTAG. per http://isitup.org/releases.mozilla.org it with that Site's ISP. RMO resolving to 184.108.40.206 works with my ISP per 1 2 ms <1 ms 1 ms 192.168.178.1 2 22 ms 22 ms 23 ms 220.127.116.11 3 23 ms 22 ms 24 ms 18.104.22.168 4 126 ms 116 ms 119 ms was-sb1-i.WAS.US.NET.DTAG.DE [22.214.171.124] 5 120 ms 121 ms 120 ms 126.96.36.199 6 188 ms 253 ms 216 ms sjc002bb01.IIJ.net [188.8.131.52] 7 307 ms 292 ms 302 ms tky001bf01.IIJ.net [184.108.40.206] 8 292 ms 299 ms 292 ms tky001ip59.IIJ.Net [220.127.116.11] 9 294 ms 293 ms 294 ms 18.104.22.168 10 290 ms 289 ms 289 ms pj-mirror01.mozilla.org [22.214.171.124] RMO resolving to e.g. 126.96.36.199 does not work, neither Domain nor IP.
Assignee: nobody → server-ops
Status: RESOLVED → REOPENED
Component: Untriaged → Server Operations
Ever confirmed: true
Product: Firefox → mozilla.org
QA Contact: shyam
Resolution: INVALID → ---
Version: 19 Branch → other
dig a +trace releases.mozilla.org goes down until: releases.mozilla.org. 60 IN CNAME releases.geo.mozilla.com. ;; Received 76 bytes from 188.8.131.52#53(184.108.40.206) in 21 ms And releases.geo.mozilla.com is NXDOMAIN for all three Mozilla nameservers (220.127.116.11, 18.104.22.168, 22.214.171.124).
For anyone who is confused as to why they can't reproduce it, it's only on some Mozilla resolvers and which resolver you hit depends on your geolocation, so this only affects a certain segment of people. It's not, however, an internal issue at specific ISPs as can be seen by the dig +trace results above.
I'm also seeing this with my isp.
Severity: normal → major
Having this problem since yesterday.
Over to infra.
Component: Server Operations → Server Operations: Infrastructure
QA Contact: shyam → jdow
geodns04 was dead. I restarted mysql and named and it seems to have recovered.
Assignee: limed → justdave
Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
(In reply to Dave Miller [:justdave] from comment #10) > geodns04 was dead. I restarted mysql and named and it seems to have > recovered. Also known as dp-geodns01, for anyone trying to figure that out in the future from this bug.
I am still having trouble completing a connection to releases.mozilla.org via FTP. I have attached the FTP log.
(In reply to David E. Ross from comment #12) > Created attachment 724799 [details] > FTP log > > I am still having trouble completing a connection to releases.mozilla.org > via FTP. I have attached the FTP log. I wanted to confirm this behaviour because it happened to me too. But after aborting that connection and retrying it after ~10 Minutes it now works just fine. ------------- Now it's NOT working again. The connection seems extremly slow and doesn't respond to aborts. "Here comes the directory listing" is the last thing I got back. Is someone working on the FTP?
(In reply to David E. Ross from comment #12) > Created attachment 724799 [details] > FTP log > > I am still having trouble completing a connection to releases.mozilla.org > via FTP. I have attached the FTP log. Created Bug 851028
Component: Server Operations: Infrastructure → Infrastructure: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.