[ale] Fedora 13 DNS weirdness

[Greg Clifton]

Well, then I suppose enlightenment is not to be found through google ;-) Or
else some other part of your anatomy needs to be googled off, perhaps your
fingers?

On Mon, Aug 9, 2010 at 12:20 AM, Joe Knapka <jknapka at kneuro.net> wrote:

>  Thanks, Jim.  Since Slackware is pissing me off by not even recognizing my
> wifi card, I'm going back to F13 for a bit.
>
> Was there some obvious place I could have found out about the need to
> restart nscd when moving between networks? (And for the love of all that's
> holy, why doesn't the all-singing, all-dancing Network Manager just do that
> automatically?)  I googled my ass off without achieving any enlightenment.
>
>
>
> On 08/09/2010 09:39 AM, Jim Kinney wrote:
>
> 'service nscd restart' is required when manually changing or resetting the
> name services supply. Once nscd is restarted on the new network, it should
> float happily between the two known networks seamlessly.
>
> if not: summit a bug as it should auto-update from a change in
> networkmanager _especially_ from the wireless portion.
>
> On Sun, Aug 8, 2010 at 11:05 PM, Joe Knapka <jknapka at kneuro.net> wrote:
>
>> I've already ditched F13 and am installing Slackware on my old Dell D600
>> laptop, but I wanted to find out if anyone can explain the following
>> totally psychotic behavior I experienced under F13:
>>
>> I set up the laptop's wifi connection on my home network using Network
>> Manager (gag,spit) and everything worked fine (?!?).
>>
>> I went to my SO's house, configured the wifi connection for her network,
>> and it connected with no problem.  I could ping the router and the
>> upstream gateway by IP or by name.  I could ping things out in the world
>> by name:
>>
>>   jk at jaklaptop:> ping google.com
>> <successful ping responses from an actual Google IP>
>>
>> However, other applications that I tried (FireFox, telnet, ssh) did this
>> (or in FF's case gave me the equivalent "I can't do that" page):
>>
>>   jk at jaklaptop:> telnet google.com 80
>>   Host google.com not found - Name or service unknown.
>>
>> Weirdly, dig and nslookup had no problem resolving google.com (or any
>> other name). But any app that I actually wanted to USE for any practical
>> purpose complained about name lookup errors, as in the telnet example
>> above.
>>
>> I checked everything in Network Manager and the two networks were
>> configured identically. I looked at /etc/resolv.conf, /etc/host.conf,
>> /etc/nsswitch.conf and everything looked totally OK -- the machine was
>> using the correct router and DNS server for my SO's network. I ran
>> tcpdump on UDP port 53 while doing a ping and a telnet, and I saw
>> successful DNS requests for google.com in both cases.... but telnet
>> still complained about "Name or service unknown". I thought maybe it was
>> something to do with SELinux, so I disabled that, but no joy.
>>
>> Then when I got home the laptop connected to my home network and
>> everything worked fine again.
>>
>> I am still at the "WTF?" stage and am not really progressing... hence
>> the switch to Slackware.  Any ideas what might have been happening here?
>>
>> Thanks,
>>
>> -- JK
>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://mail.ale.org/mailman/listinfo/ale
>> See JOBS, ANNOUNCE and SCHOOLS lists at
>> http://mail.ale.org/mailman/listinfo
>>
>
>
>
> --
> --
> James P. Kinney III
> I would rather stumble along in freedom than walk effortlessly in chains.
>
>
>
> _______________________________________________
> Ale mailing listAle at ale.orghttp://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists athttp://mail.ale.org/mailman/listinfo
>
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20100809/af92990a/attachment.html