If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

DNS: hosts file entry for host on local subnet ignored (firebird 0.6.1)

RESOLVED EXPIRED

Status

()

Core
Networking
RESOLVED EXPIRED
14 years ago
12 years ago

People

(Reporter: Jim Bennett, Assigned: Darin Fisher)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6

Similar bugs have been reported for <b>Mozilla</b> (<a
href="http://bugzilla.mozilla.org/show_bug.cgi?id=186453>186453</a>, <a
href="http://bugzilla.mozilla.org/show_bug.cgi?id=195823>195823</a>, <a
href="http://bugzilla.mozilla.org/show_bug.cgi?id=204955>204955</a>) but none
have been reported for <b>firebird</b>. <p>Firebird 0.6.1 seems to ignore
c:\winnt\system32\drivers\etc\hosts entries, at least those for hosts on the
local subnet. IE 6, run on the same box, does not have this problem. As a
result, firebird 0.6.1 can't resolve URL using the host name specified in the
hosts file, while IE 6 can.</p>

Reproducible: Always

Steps to Reproduce:
1. assume your local subnet is 111.222.333.x
2. put an entry in c:\winnt\system32\drivers\etc\hosts for a host on this
subnet, e.g. "111.222.333.2 MyLinuxBox"
3. fire up firebird 0.6.1. Direct firebird to "http://MyLinuxBox".
Actual Results:  
a. firebird tries to resolve this URL for awhile and then goes out to the
internet to try to find something close, returning something like
http://my.stupidsite.com/MyLinuxBox.html.
b. Try the same thing in IE 6.
c. IE 6 immediately resolves the host correctly, as specified in
c:\winnt\system32\drivers\etc\hosts


Expected Results:  
Firebird should have checked c:\winnt\system32\drivers\etc\hosts, found the
entry for MyLinuxBox, and resolved the URL http://MyLinuxBox to 111.222.333.2,
as listed in that hosts entry.
(Reporter)

Comment 1

14 years ago
sorry about the extraneous html tags; I'm a bugzilla newbie.
(Reporter)

Comment 2

14 years ago
This occured on my office box, which might be running firebird 0.6 instead of
0.6.1. Will double check on Aug 11 03

Comment 3

14 years ago
Backend issue. -> DUPE

*** This bug has been marked as a duplicate of 195823 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → DUPLICATE

Comment 4

14 years ago
REOPEN: Most of 195823 is Mac-only
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---

Comment 5

14 years ago
Reassigning
Assignee: blake → darin
Component: General → Networking
Product: Firebird → Browser
QA Contact: asa → benc
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: 14 years ago12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.