No nscd as far as I can tell.
On Mon, 15 Jul 2013 07:01:56 +1000, Igor Cicimov wrote:
> Do you have nscd running by any chance?
Doesn't look like, unless it hides under an alias:
root@notlookedfor:/home/hendrik# ps -Al | grep nscd
root@notlookedfor:/home/hendrik#
-- hendrik
> On 15/07/2013 12:58 AM, "Hendrik Boom" <hendrik@topoi.pooq.com> wrote:
>
>> On Sat, 13 Jul 2013 16:53:01 -0400, staticsafe wrote:
>>
>> > On Sat, Jul 13, 2013 at 08:39:10PM +0000, Hendrik Boom wrote:
>> >> For some reason, chromium seems to have got it stuck in its head
>> >> that slashdot,org is at 69.165.131.134. At least, when I try to
>> >> browse to slashdot.org using chromium, the displayed contents are
>> >> identical to the contents at 16.165.131.134, which contains my
>> >> personal web site.
>> >>
>> >> Firefox and chrome have no trouble reaching the real site.
>> >>
>> >> And I can read slashdot just fine on chromium if I enter the IP
>> >> number 216.34.181.45 instead of the domain name.
>> >>
>> >> So I'm guessing that chromium has got that IP number stuck in some
>> >> internal DNS cache.
>>
>> It now looks as if chromium's DNS cache may not be the problem.
>> Chromium must be getting slashdot's IP address from somewhere else --
>> somewhere that firefox and ping don't access.
>>
>>
>> >> How can I get it to forget it?
>> >>
>> >> -- hendrik
>> >
>> > Navigate to chrome://net-internals/#dns and press the "Clear host
>> > cache"
>> > button.
>>
>> After navigating there from chromium and pressing the button,
>> slashdot.org doesn't appear in the listing of the cache entries on that
>> page.
>>
>> But the misbehaviour still persists, even after a reboot.
>>
>> And firefox and chrome and ping still reach the right site.
>>
>> And when I go to chrome://net-internals/#dns on chrome itself, it tells
>> mem it *does* have slashdot.org in its cache, with the right IP number.
>>
>> The cache chromium reveals with chrome://net-internals/#dns clearly has
>> different contents from the one that chrome reveals -- which confirms
>> that they have different caches.
>>
>> And even after browsing to slashdot.org in chromium and getting to the
>> wrong place, going to chrome://net-internals/#dns with chromium still
>> indicates that slashdot.org is not in the cache.
>>
>> So I'm suspecting that chrome://net-internals/#dns may not reeveal the
>> real cache in chromium.
>>
>> So where *is* chromium getting this misinformation?
>>
>> Just for reference, here's my /etc/resolv.conf file:
>>
>> # Generated by NetworkManager domain topoi.pooq.com search
>> topoi.pooq.com nameserver 8.8.8.8 nameserver 8.8.4.4
>>
>>
>> -- hendrik
>>
>>
>> > Source -
>> > http://superuser.com/a/203702
>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
>> subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>> Archive: [🔎] krue89$l0o$1@ger.gmane.org">http://lists.debian.org/[🔎] krue89$l0o$1@ger.gmane.org
>>
>>
> <p dir="ltr">Do you have nscd running by any chance?<br>
> </p>
> <div class="gmail_quote">On 15/07/2013 12:58 AM, "Hendrik
> Boom" <<a
> href="mailto:hendrik@topoi.pooq.com";>hendrik@topoi.pooq.com</a>>
> wrote:<br type="attribution"><blockquote class="gmail_quote"
> style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> On Sat, 13 Jul 2013 16:53:01 -0400, staticsafe wrote:<br>
> <br>
> > On Sat, Jul 13, 2013 at 08:39:10PM +0000, Hendrik Boom wrote:<br>
> >> For some reason, chromium seems to have got it stuck in its
> head that<br>
> >> slashdot,org is at 69.165.131.134. At least, when I try to
> browse to<br>
> >> <a href="http://slashdot.org"; target="_blank">slashdot.org</a>
> using chromium, the displayed contents are identical to<br>
> >> the contents at <a href="tel:16.165.131.134"
> value="+16165131134">16.165.131.134</a>, which contains my personal web
> site.<br>
> >><br>
> >> Firefox and chrome have no trouble reaching the real site.<br>
> >><br>
> >> And I can read slashdot just fine on chromium if I enter the IP
> number<br>
> >> <a href="tel:216.34.181.45"
> value="+12163418145">216.34.181.45</a> instead of the domain name.<br>
> >><br>
> >> So I'm guessing that chromium has got that IP number stuck
> in some<br>
> >> internal DNS cache.<br>
> <br>
> It now looks as if chromium's DNS cache may not be the problem.
> Chromium<br>
> must be getting slashdot's IP address from somewhere else --
> somewhere<br>
> that firefox and ping don't access.<br>
> <br>
> >><br>
> >> How can I get it to forget it?<br>
> >><br>
> >> -- hendrik<br>
> ><br>
> > Navigate to chrome://net-internals/#dns and press the "Clear
> host cache"<br>
> > button.<br>
> <br>
> After navigating there from chromium and pressing the button, <a
> href="http://slashdot.org"; target="_blank">slashdot.org</a><br>
> doesn't appear in the listing of the cache entries on that page.<br>
> <br>
> But the misbehaviour still persists, even after a reboot.<br>
> <br>
> And firefox and chrome and ping still reach the right site.<br>
> <br>
> And when I go to chrome://net-internals/#dns on chrome itself, it
> tells<br>
> mem it *does* have <a href="http://slashdot.org";
> target="_blank">slashdot.org</a> in its cache, with the right IP
> number.<br>
> <br>
> The cache chromium reveals with chrome://net-internals/#dns clearly
> has<br>
> different contents from the one that chrome reveals -- which
> confirms<br>
> that they have different caches.<br>
> <br>
> And even after browsing to <a href="http://slashdot.org";
> target="_blank">slashdot.org</a> in chromium and getting to the<br>
> wrong place, going to chrome://net-internals/#dns with chromium
> still<br>
> indicates that <a href="http://slashdot.org";
> target="_blank">slashdot.org</a> is not in the cache.<br>
> <br>
> So I'm suspecting that chrome://net-internals/#dns may not reeveal
> the<br>
> real cache in chromium.<br>
> <br>
> So where *is* chromium getting this misinformation?<br>
> <br>
> Just for reference, here's my /etc/resolv.conf file:<br>
> <br>
> # Generated by NetworkManager<br>
> domain <a href="http://topoi.pooq.com";
> target="_blank">topoi.pooq.com</a><br>
> search <a href="http://topoi.pooq.com";
> target="_blank">topoi.pooq.com</a><br>
> nameserver 8.8.8.8<br>
> nameserver 8.8.4.4<br>
> <br>
> <br>
> -- hendrik<br>
> <br>
> ><br>
> > Source -<br>
> > <a href="http://superuser.com/a/203702";
> target="_blank">http://superuser.com/a/203702</a><br>
> <br>
> <br>
> <br>
> --<br>
> To UNSUBSCRIBE, email to <a
> href="mailto:debian-user-REQUEST@lists.debian.org";>debian-user-
REQUEST@lists.debian.org</a><br>
> with a subject of "unsubscribe". Trouble? Contact <a
> href="mailto:listmaster@lists.debian.org";>listmaster@lists.debian.org</
a><br>
> Archive: <a href="[🔎] krue89$l0o$1@ger.gmane.org"">http://lists.debian.org/[🔎] krue89$l0o$1@ger.gmane.org";
> target="_blank">[🔎] krue89$l0o$1@ger.gmane.org">http://lists.debian.org/[🔎] krue89$l0o$1@ger.gmane.org</
a><br>
> <br>
> </blockquote></div>
Reply to: