Closed
Bug 157005
Opened 23 years ago
Closed 23 years ago
DNS: resolution with large responses does not complete
Categories
(Core :: Networking, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: aeriksson, Unassigned)
Details
check out http://ftp.us.kernel.org/. The browser (1.0rc2) hangs forever trying
to resolve the name. A check with nslookup shows:
<shell>$ nslookup ftp.us.kernel.org
Note: nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead. Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
;; Truncated, retrying in TCP mode.
Server: 10.0.1.254
Address: 10.0.1.254#53
Non-authoritative answer:
Name: ftp.us.kernel.org
Address: 128.193.4.3
Name: ftp.us.kernel.org
Address: 128.223.162.20
Name: ftp.us.kernel.org
Address: 129.21.60.34
Name: ftp.us.kernel.org
Address: 129.74.32.155
Name: ftp.us.kernel.org
Address: 140.221.9.138
Name: ftp.us.kernel.org
Address: 144.92.9.246
Name: ftp.us.kernel.org
Address: 146.186.15.46
Name: ftp.us.kernel.org
Address: 150.208.72.11
Name: ftp.us.kernel.org
Address: 155.101.16.102
Name: ftp.us.kernel.org
Address: 157.91.30.122
Name: ftp.us.kernel.org
Address: 198.186.202.139
Name: ftp.us.kernel.org
Address: 204.157.9.31
Name: ftp.us.kernel.org
Address: 206.10.253.14
Name: ftp.us.kernel.org
Address: 206.253.222.50
Name: ftp.us.kernel.org
Address: 207.45.221.24
Name: ftp.us.kernel.org
Address: 207.250.4.12
Name: ftp.us.kernel.org
Address: 209.140.211.22
Name: ftp.us.kernel.org
Address: 209.221.142.122
Name: ftp.us.kernel.org
Address: 216.17.145.149
Name: ftp.us.kernel.org
Address: 216.176.132.235
Name: ftp.us.kernel.org
Address: 24.220.0.37
Name: ftp.us.kernel.org
Address: 35.9.25.26
Name: ftp.us.kernel.org
Address: 64.39.15.173
Name: ftp.us.kernel.org
Address: 128.2.4.139
Name: ftp.us.kernel.org
Address: 128.105.1.37
Name: ftp.us.kernel.org
Address: 128.121.238.137
Name: ftp.us.kernel.org
Address: 128.153.4.60
which makes me think that perhaps mozilla (which has its own dns resolver,afaik)
does not handle large DNS responses correctly.
I'm runing on rehad 7.2, with
mozilla-nss-1.0rc2-0
mozilla-js-debugger-1.0rc2-0
mozilla-psm-1.0rc2-0
mozilla-1.0rc2-0
mozilla-dom-inspector-1.0rc2-0
mozilla-nss-devel-1.0rc2-0
mozilla-nspr-1.0rc2-0
mozilla-devel-1.0rc2-0
mozilla-nspr-devel-1.0rc2-0
mozilla-chat-1.0rc2-0
mozilla-mail-1.0rc2-0
Hope this helps!
/Anders
Comment 1•23 years ago
|
||
wfm with win2k build 20020710..
Reporter:
Your build is too old. -> invalid
Please reopen if you see this with a recent build from mozilla.org. (1.1a or later)
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
we don't have a resolver, but we do have some higher-level caching.
Putting a large, (likely TCP-transfered) request into the testcases is something
I have wanted to do for a long time.
Summary: DNS resolution with large responses does not complete → DNS: resolution with large responses does not complete
REOPEN: I'd like a WFM in linux. This could be a platform specific problem.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Whiteboard: checklinux
WORKSFORME. Linux RedHat 7.2, Moz 1.0.1 and current trunk.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•