Re: SuSE 10.1 - Networking blarney
- From: Chris Wilkinson <blobster@xxxxxxxxxxxxxx>
- Date: Sat, 08 Jul 2006 18:29:04 +1000
Hi there,
John Sandell wrote:
Blobster_NZ wrote:
Hi there,
I have yet another networking issue (why me?), which is why I'm posting
from poxy
Google Groups! :-)
SuSE 10.1 is on my main machine. I have eth0 connected to my new DSL
router
and eth1 connected to my Kubuntu/WinXP box. This all worked brilliantly
a few days
ago, but now most web addresses I enter take upwards of 20-30 seconds
to resolve,
and things like news servers time out. I suspected my old router
(D-Link DSL-502T)
was on the fritz, so bought a Netgear DG632 this morning...it showed
the exact same
symptoms! :-(
Out of curiosity I booted Kubuntu LiveCD 6.06 on my SuSE box, and lo
and behold all
DNS resolve and other activity is instantaneous again, when browsing
from that!
SuSE has obviously munted its own network/route/DNS settings, although
nothing
was changed or appears to have changed from when it worked brilliantly
a few days
ago. What I want to know is what can I do to completely delete and
restore any/all
network software in SuSE? I wanna completely reload any network code on
the
entire SuSE box to try and resurrect my networking.
Could zeroconf affect my DNS like that? There is a stray 169.254.0.0
address listed
in my route table that I suspect is from zeroconf.
OK, can anyone help here? This SuSE networking instability is annoying
me...
<sigh!> :-(
--
Kind regards,
Chris Wilkinson, Brisbane, Australia.
...coming to you from Google Groups, since SuSE has munted my usenet
access!
Is network startup messing with your /etc/resolv.conf file?
As it turns out resolv.conf was the key to it. I'm not sure
what it looked like prior, but docs told me point dns querys
to the router address, not a known dns server, as the router
was supposed to find my ISP's dns nameservers. Turns out that
both routers did find the nameservers, but for some reason I
could not resolve names just by sending DNS querys to router:
it needed to go direct to the nameservers...
S'funny but I've never ever setup dns to go direct to known
dns servers, only to my router of choice...why it stops being
able to resolve names now I'm still stumped on, but putting
the ISP's dns servers into resolv.conf has fixed the resolve
problem... <sigh!>
--
Kind regards,
Chris Wilkinson, Brisbane, Australia.
Anyone wishing to email me directly can remove the obvious
spamblocker, and replace it with t p g <dot> c o m <dot> a u
.
- Follow-Ups:
- Re: SuSE 10.1 - Networking blarney
- From: Mike Fields
- Re: SuSE 10.1 - Networking blarney
- From: Chris Wilkinson
- Re: SuSE 10.1 - Networking blarney
- References:
- SuSE 10.1 - Networking blarney
- From: Blobster_NZ
- Re: SuSE 10.1 - Networking blarney
- From: John Sandell
- SuSE 10.1 - Networking blarney
- Prev by Date: Re: Discover machines on local network
- Next by Date: Re: Tux Racer Gone :(
- Previous by thread: Re: SuSE 10.1 - Networking blarney
- Next by thread: Re: SuSE 10.1 - Networking blarney
- Index(es):
Relevant Pages
|
Loading