Kristian Kielhofner wrote: > On Wed, Oct 29, 2008 at 9:36 AM, Rob Hillis <[EMAIL PROTECTED]> wrote: > >> Rob Hillis wrote: >> >>> Ping times to >>> >> My apologies for not finishing my train of thought here. :) Ping times >> to my DNS server are between 0.15 and 0.2ms with the *very* occasional >> longer delay of up to 0.4ms. >> > What happens when you use dig @$DNS www.google.com.au, etc from > another machine on the local network? Your DNS server indeed does > seem very local. However, ping times measure network latency from one > kernel to the other, not taking into account the application, daemon, > etc that's running the service you're trying to connect to (DNS, in > this case). While it's probably not the problem, it's quite possible > your upstream DNS server could be having some issues returning > records. dig will tell you how long it takes to return the record. >
About 188ms. :) Given that I wasn't having problems with DNS resolution on any other machine on the network, I doubted my DNS server was at fault. The output is as follows:- ws1 ~ # dig @192.168.1.10 www.google.com.au ; <<>> DiG 9.5.0-P2 <<>> @192.168.1.10 www.google.com.au ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49224 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 7, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.google.com.au. IN A ;; ANSWER SECTION: www.google.com.au. 183907 IN CNAME www.google.com. www.google.com. 443105 IN CNAME www.l.google.com. www.l.google.com. 300 IN A 66.249.89.104 www.l.google.com. 300 IN A 66.249.89.147 www.l.google.com. 300 IN A 66.249.89.99 ;; AUTHORITY SECTION: l.google.com. 10834 IN NS b.l.google.com. l.google.com. 10834 IN NS a.l.google.com. l.google.com. 10834 IN NS f.l.google.com. l.google.com. 10834 IN NS g.l.google.com. l.google.com. 10834 IN NS d.l.google.com. l.google.com. 10834 IN NS c.l.google.com. l.google.com. 10834 IN NS e.l.google.com. ;; Query time: 188 msec ;; SERVER: 192.168.1.10#53(192.168.1.10) ;; WHEN: Thu Oct 30 12:11:26 2008 ;; MSG SIZE rcvd: 243 I've tried resolving several different DNS entries with results varying from 100 to 300ms. > With that being said, there are some known issues with DNS (especially > failure between servers) in uClibc. These are pretty well established > and we've known about them for some time, the problem is, you can't > just upgrade the C library whenever you feel like it :). We have some > plans to upgrade to the latest uClibc (0.9.30), I believe, in trunk. > I haven't looked at any Changelogs yet but I'm hoping newer versions > will have a more robust resolver. > This is sounding very much like the problem here. If this is the case, I'll keep my version of Astlinux well up-to-date until this problem is resolved. Not quite the answer I wanted to hear, but I *have* chosen to run a pre-release version - so I have no-one to blame but myself. :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
