[ale] incorrect /etc/resolv.conf after switching provider

[JK]

Minor correction: I'm Joe Knapka, not Jim Kinney.  Don't let the fact
that you've never seen both of us in the same room bother you at all.
Jim and I did meet once, and there were no strange effects a la
matter/antimatter, so I'm reasonably confident that we are distinct
individuals. (Remember Jim, I bought that 15MB monster of a SCSI
disk from you back in like 1993 or so? Picked it up in the parking
lot of some building on the Emory campus, I think.)

-- JK


Omar Chanouha wrote:
> Wireshark confirmed that it is the router sending the incorrect DNS info.
> 
> Jim, the response was still appreciated and interpreted properly, no worries.
> 
> Now I just have to figure out why the router isn't updating it's DNS
> cache properly and fix it... or just reset it.
> 
> thanks,
> 
> -O
> 
> On Wed, Jul 15, 2009 at 3:43 PM, JK<jknapka at kneuro.net> wrote:
>> JK wrote:
>>> JK wrote:
>>>> Omar Chanouha wrote:
>>>>> Can anyone tell me where dhcpcd is getting this information? Is it the
>>>>> router(linksys)? Is it in a cache somewhere?
>>>>
>>>> I think we'd need to know more about your network setup to answer
>>>> this question with any confidence.  Idle speculation follows, starting
>>>> with the observation that the resolv.conf text implies you're
>>>> running DHCP on a wireless interface, which in turn implies you
>>>> are using a wifi router between your Linux box and your ISP's
>>>> uplink.
>>>
>>> And, durrr, you also said that :-p
>>
>> And finally, because I realized after hitting "Send" that the comment above
>> could be misinterpreted, and because sending self-followups is my favorite
>> thing EVER, I feel I should point out that those words were meant to be entirely
>> self-deprecating.  The gist is: "Gee, I'm such a dummy for not noticing
>> (or else immediately forgetting) Omar's clear statement that he is, in
>> fact, using a Linksys router, before sending my overly-verbose reply
>> predicated upon some uncertainty as to whether or not that might be the
>> case."  Or more concisely, "durrr".
>>
>> Even if I notice some obscure opportunity for THIS post to be misinterpreted,
>> I promise not to send another post correcting it. Really.
>>