[prev] [thread] [next] [lurker] [Date index for 2003/08/12]
So here's a not uncommon story. When I'm at home the local name server resolves http://hates-software.com as having an address just this side of the router. Webpages happen. I break free of the sofa magnetic pull, and take my laptop with me. Because I'm now talking to a different nameserver I get handed the address of the smoothwall router, when I do dns lookups, so ssh and everything else sane just works. Switch to the web browser, and it sits there and looks at me funny and then tells me that the connection timed out. "Funny, " I think, "this ssh session seems responsive and telnetting to port 80 on the box is working" And then you realise, it's being hateful again. The web browser has cached the results of a dns query internally. Internally - what don't you trust the resolver in the os to give that a go? Not only that, the only way to clear it is to quit the app and restart it. Yes mozilla, I'm looking at you, and all your bastard offspring, I have a few words to say to you. STUPID! STUPID! I WAS USING THAT BROWSER, AND YOU MADE ME KILL IT! STUPID! STUPID! ARGH! I DIDN'T HAVE EVERYTHING CAREFULLY BOOKMARKED, BECAUSE YOUR BOOKMARK SYSTEM SUCKS TOO! STUPID! One again the web seeks my destruction, even more than I seek its. -- Richard Clamp <richardc@xxxxxxxxx.xxx>
Generated at 14:02 on 01 Jul 2004 by mariachi 0.52