Closed Bug 160716 Opened 23 years ago Closed 23 years ago

DNS: lookups fail after some time

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
Sun
Solaris
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: terra, Unassigned)

References

(
URL
)

Details

(Keywords: helpwanted, Whiteboard: [not a mozilla bug?])

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.1b) Gecko/20020729 BuildID: 2002072922 My browser often (once a day) manages to get itself into a state where all DNS lookups fail with the message "UNRESOLVED_HOSTNAME". At that point, it's exit and restart time. Reproducible: Sometimes Steps to Reproduce: 1. Browse... 2. Observe DNS failures 3. Verify that machine's dns is working fine from some xterm window, for example. 4. Exit and restart mozilla. Actual Results: "Problem Report The system detected an Unresolved Host Name while attempting to retrieve the URL: http://www.mozilla.org/quality/help/bug-form.html. Message ID UNRESOLVED_HOSTNAME [...]" There is no obvious trigger for this.
are you using nscd?
Whiteboard: checkmac, checklinux, checkwin
Nope. /etc/resolv.conf contains the ip addresses of three on-site dns servers. Note, that only mozilla is affected. While it is affected, other applications on the machine work just fine dns-wise.
I've never had this problem on Linux RedHat 7.3, in about 3 months of using Mozilla every day. The only times I've gotten a DNS lookup error was when the domain name was invalid or the DNS server was truly unreachable by the whole machine. Consider this "checklinux" feedback.
Benjamin: correction. It appears that I am using nscd. Here are the open files at a time when mozilla was in this state. Note the "8r" file: a door to nscd. (And what the heck is "26r" good for?) Does strace and truss on the running mozilla reveals nothing interesting. The only errors occurring are EAGAIN and ERESTART (Error 91). Anything else to look for next time? mozilla-b 10270 welinder 2u VCHR 24,2 0t62376 292599 /devices/pseudo/pts@0:0->ttcompat->ldterm->ptem->pts mozilla-b 10270 welinder 3u FIFO 0x30002570620 0t1 5346 PIPE->0x30002570708 mozilla-b 10270 welinder 4u FIFO 0x30002570708 0t1 5346 PIPE->0x30002570620 mozilla-b 10270 welinder 5u VCHR 24,2 0t62376 292599 /devices/pseudo/pts@0:0->ttcompat->ldterm->ptem->pts mozilla-b 10270 welinder 6u VREG 262,53 501 387900 /scratch/welinder (yeti:/export/scratch/share/welinder) mozilla-b 10270 welinder 7u FIFO 0x300037e50c0 0t192 5345 PIPE->0x3000215b620 (FA:->0x30001bff7e0) mozilla-b 10270 welinder 8r DOOR 0,34 0t0 57328 door to nscd[224] mozilla-b 10270 welinder 9u FIFO 0x3000215a020 0t1 5347 PIPE->0x3000215a108 mozilla-b 10270 welinder 10u FIFO 0x3000215a108 0t1 5347 PIPE->0x3000215a020 mozilla-b 10270 welinder 11r VREG 262,53 294222 11813821 /scratch/welinder (yeti:/export/scratch/share/welinder) mozilla-b 10270 welinder 12r VREG 262,53 697431 11813807 /scratch/welinder (yeti:/export/scratch/share/welinder) mozilla-b 10270 welinder 13r VREG 262,53 4923 11813816 /scratch/welinder (yeti:/export/scratch/share/welinder) mozilla-b 10270 welinder 14u IPv4 0x300037e5728 0t7252 TCP robbie:50968->kit:9990 (ESTABLISHED) mozilla-b 10270 welinder 15u FIFO 0x3000215b820 0t0 5348 PIPE->0x3000215b908 mozilla-b 10270 welinder 16u FIFO 0x3000215b908 0t0 5348 PIPE->0x3000215b820 mozilla-b 10270 welinder 17r VREG 262,53 904407 11813815 /scratch/welinder (yeti:/export/scratch/share/welinder) mozilla-b 10270 welinder 18r VREG 262,53 226454 11813818 /scratch/welinder (yeti:/export/scratch/share/welinder) mozilla-b 10270 welinder 19r VREG 262,53 22655 11813820 /scratch/welinder (yeti:/export/scratch/share/welinder) mozilla-b 10270 welinder 20r VREG 262,53 106468 11813853 /scratch/welinder (yeti:/export/scratch/share/welinder) mozilla-b 10270 welinder 21u VREG 136,7 256811 1222132 /export/home/welinder/.mozilla/welinder/10wln2xa.slt/history.dat mozilla-b 10270 welinder 22u VREG 136,7 135168 1420155 /export/home/welinder/.mozilla/welinder/10wln2xa.slt/Cache/_CACHE_MAP_ mozilla-b 10270 welinder 23u VREG 136,7 512512 1420194 /export/home/welinder/.mozilla/welinder/10wln2xa.slt/Cache/_CACHE_001_ mozilla-b 10270 welinder 24u VREG 136,7 8192 1420207 /export/home/welinder/.mozilla/welinder/10wln2xa.slt/Cache/_CACHE_002_ mozilla-b 10270 welinder 25u VREG 136,7 4096 1420208 /export/home/welinder/.mozilla/welinder/10wln2xa.slt/Cache/_CACHE_003_ mozilla-b 10270 welinder 26r IPv4 0x300037e5368 0t0 UDP *:* (Unbound) mozilla-b 10270 welinder 27u VREG 136,7 32768 1222134 /export/home/welinder/.mozilla/welinder/10wln2xa.slt/cert7.db mozilla-b 10270 welinder 28u VREG 136,7 32768 1222135 /export/home/welinder/.mozilla/welinder/10wln2xa.slt/key3.db mozilla-b 10270 welinder 30r VREG 262,53 485149 11813856 /scratch/welinder (yeti:/export/scratch/share/welinder)
+helpwanted, cc:neeti (do we have any solaris people we can CC?) I don't know if any of those tools will show anything useful. I've used truss a lot from my server days, but not for DNS problems. You probably want to turn on truss after you see the problem, try a DNS lookup that fails, then turn truss off. It can generate a lot of output. As for nscd, I asked because I've noticed that there are only two campus on ncsd. One says always turn it off, the other says always leave it on. Nobody has ever gotten them in a single room to reconcile this, so my suggestion is to turn it off for a while and see what happens.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: helpwanted
Whiteboard: checkmac, checklinux, checkwin → checkmac, checkwin
cc'ing darin
reporter: are you by any chance using a http proxy server? does the DNS failure appear as a popup error message or as a document in the browser window?
There is a proxy server (junkbuster) in action. (Using HTTP/1.0.) I get a mozilla-generated web page -- a grey table -- which I pasted into the original message. (Very different from when I visit http://oinkoinkoink.oink/ and get a junkbuster-generated white page from junkbuster saying "No such domain: oinkoinkoink.oink".) I haven't actually seen this problem for more than a week, knock on wood. I am still running the same build.
If you get an error displayed as a page, it is probably an error from your proxy server... can you save the source and attach it to the bug?
Summary: DNS lookups fail after some time → DNS: lookups fail after some time
Googling a bit reveal the pages http://www.geocities.com/pioneersoftsite/ http://ruruis.hoops.ne.jp/ http://msgs.securepoint.com/cgi-bin/get/bugtraq0207/198.html (Just type "Problem Report the system detected an Unresolved Host Name while attempting" into google.) Note the bugtraq link: CacheFlow might be the cause.
I looked at the public examples, and they happen for me in IE as well, but I don't think they are the real problem. The real problem is your interaction with something that is producing the error. Getting the HTML of the error is the next step.
Whiteboard: checkmac, checkwin
Well, I would give you the source if I could, but obviously the error does not happen right now, :-| I am however sure, that if you take the geocities link and truncate whatever GeoCities append, then you have it. My current guess: not a Mozilla issue. Someone upstream (not onsite, I am told) is running a caching proxy server called CacheFlow. That proxy gets into a funny state. Maybe I get a different proxy if I exit and reconnect. Please downgrade severity.
Severity: major → minor
Whiteboard: [not a mozilla bug?]
RESOLVED/INVALID: If you find this happens just in mozilla, and not other browsers, then we'd want to look at this further. Based on the current information, if you agree this isn't a mozilla problem, please mark this "VERIFIED"
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Verified, it is.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.