connect failure on stale cached resolved ip

RESOLVED EXPIRED

Status

()

RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: marc, Assigned: darin.moz)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8

Google took one of its servers out of service.  The ip addr seemed to be cached
and foxfire didn't perform a fresh lookup before giving up on connecting saying
"google.com could not be found, please check the name and try again"

nslookup found an ip for www.google.com, ping proved it alive.

Reproducible: Always
Steps to Reproduce:
1.find a server that will be taken out of service
2.dns resolve that server
3.try to connect to the server once its been taken out

Actual Results:  
"google.com could not be found, please check the name and try again"


Expected Results:  
Perhaps if one can't find a route to a host one might try re-resolving.  Perhaps
it is google.com that is taking their servers out of service prior to the
expiration of their TTL.  Perhaps a good failsafe would be to try to initiate a
fresh dns lookup after connection failure with the dns server responsible for
the domain in question and if the results are different attempt to connect there.

Updated

15 years ago
Assignee: firefox → darin
Component: General → Networking: HTTP
Product: Firefox → Browser
QA Contact: core.networking.http
Version: unspecified → Trunk
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.