Closed
Bug 276835
Opened 20 years ago
Closed 19 years ago
Firefox can't resolve intranet hostname
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: lsohil, Assigned: darin.moz)
References
()
Details
I am trying to access the above mentioned web site through FireFox browser, but
I get the following message:
===================================================================================
The requested URL could not be retrieved
While trying to retrieve the URL: punepmo:443
The following error was encountered:
Unable to determine IP address from host name for punepmo
The dnsserver returned:
Server Failure: The name server was unable to process this query.
This means that:
The cache was not able to resolve the hostname presented in the URL.
Check if the address is correct.
Your cache administrator is root.
===================================================================================
This works through IE browser though. Please note that I have already imported
the settings from IE to Firefox.
further this website is an "intranet" site.
Comment 1•20 years ago
|
||
Changing summary from "Web site accessing" to "Firefox can't resolve intranet hostname". Over to Networking.
Assignee: firefox → darin
URL: https://punepmo → https://punepmo/
Component: General → Networking
Product: Firefox → Core
QA Contact: firefox.general → benc
Summary: Web site accessing → Firefox can't resolve intranet hostname
Version: 1.0 Branch → Trunk
Comment 2•20 years ago
|
||
do you have any "No proxy for" entries listed in options/general/connection settings?
Do you know the domain name of punepmo? Can you try https://punempo.whatever.tld/ ?
Comment 4•19 years ago
|
||
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/
Comment 5•19 years ago
|
||
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
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•