Closed
Bug 606826
Opened 15 years ago
Closed 15 years ago
Mozilla web properties have flakey DNS
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: khuey, Unassigned)
Details
A number of Mozilla's web properties seem to disappear from the internet for about 10 minutes at a time for me. For example, I'll be unable to resolve bugzilla.mozilla.org, but tracert to 63.245.209.72 works fine. I've seen this happen to bugzilla, planet and MXR regularly, and I think tbpl once. I'm fairly sure it's not on my end because I've had it happen in several different cities on multiple machines. I also don't see anything like this with non-Mozilla sites.
Comment 1•15 years ago
|
||
You need to provide more information, preferably with different OSes/machines or resolvers for us to even consider that it's a problem on our end.
Try using host, dig on linux or nslookup on windows when you're facing the problem and paste the solution.
Also, paste your DNS servers here..and if you use a resolver on your router or wireless modem, that would be useful too.
Do you by any chance have DNSSEC enabled/validating resolvers?
Comment 2•15 years ago
|
||
(In reply to comment #1)
> Try using host, dig on linux or nslookup on windows when you're facing the
> problem and paste the solution.
I meant response. Bah.
> Also, paste your DNS servers here..and if you use a resolver on your router or
> wireless modem, that would be useful too.
paste your DNS servers, bleh. Can you pass on your DNS configs? What DNS servers you're using, also if you're on the VPN or not when this happens?
Updated•15 years ago
|
Status: NEW → UNCONFIRMED
Ever confirmed: false
| Reporter | ||
Comment 3•15 years ago
|
||
And of course after hitting it multiple times a day since I filed this I haven't hit it once. I'll reopen if it happens again.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•