Am Di, den 28.06.2005 schrieb Jacques-Andre Boulay um 22:52: > > $ dig www.google.com +trace @192.5.6.30 > > > > If you query this way, does it resolve faster then? Or try following > > > > dig www.google.com +trace @198.235.216.130 > > No, same response time! Ok. > > Got the last DNS IP from "$ host -t ns bellnexxia.net". > > bellnexxia.net name server ns4.bellglobal.com. You misunderstood me here. I just wanted to tell you where I got the IP from which you should try running dig. > > And a last question: You didn't say that clearly, but browsing with your > > Windows® client is as slow regarding response time. I guess so. > > No, that's what is strange: it's really faster... Ok, that is an important fact. It tells us that the problem is not with the remote DNS server but within your on local network. Did you compare the TCP settings your Windows® host has with the settings of your Fedora box? You may too run following: a) in one terminal as root run: tcpdump -X -i eth0 port 53 b) in another terminal run as normal user: dig www.google.com +trace @206.47.244.57 The output of the tcpdump command will hopefully show us where the problem is. Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 23:01:37 up 3 days, 5:53, load average: 0.08, 0.20, 0.26
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
