This is a discussion on Re: 1 second delay - more detail and specifics within the Bind Users forums, part of the DNS and Related Forums category; OK, db, via the search, resolves to db.gns.gnumber.com, which is a CNAME for gnumber1.gns.gnumber.com. ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
OK,
db, via the search, resolves to db.gns.gnumber.com, which is a CNAME for gnumber1.gns.gnumber.com. If I do "time host db" it takes 1.024 seconds when pointed to 127.0.0.1. If I do "time host db.gns.gnumber.com" it takes 0.012 seconds when pointed to 127.0.0.1. Why the big delta????? search gns.gnumber.com should make these lookups identical, or make it two lookups. If I do "time host db" it takes 0.020 seconds when pointed to 207.200.55.226. If I do "time host db.gns.gnumber.com" it takes 0.020 seconds when pointed to 207.200.55.226. Since search make this the first or second lookup, this is what I'd expect. entire /etc/named.conf: ------------------------- options { directory "/var/named"; // use /var/named pid-file "/var/run/named/named.pid"; listen-on port 53 { 127.0.0.1; }; }; zone "0.0.127.IN-ADDR.ARPA" { type master; file "127.0.0"; }; zone "." { type hint; // used to be specified w/ "cache" file "root.servers.hints"; }; include "/etc/dns.keys.conf"; ------------------------- resolv.conf: ------------------------- ; generated by /sbin/dhclient-script search gns.gnumber.com nameserver 127.0.0.1 nameserver 207.200.55.226 nameserver 66.98.210.85 nameserver 12.96.160.115 ------------------------- On Mon, May 30, 2005 at 02:42:53AM -0700, Bryan Irvine wrote: > You should post your conf files. Won't get far without those. > > --Bryan > > On 5/28/05, Wayne Walker <wwalker@bybent.com> wrote: > > I have a number of servers that need fast lookups. I set up BIND named > > on each one weeks ago, and changed /etc/resolv.conf to have 127.0.0.1 as > > the first nameserver line. > > > > They were running fine with ~500 ms lookups the first time for any host > > in our domain. Subsequent lookups for the same host were always in the > > 7-15 ms range! :) > > > > Starting yesterday, at least 2 of the servers are now getting an > > addition full second of delay talking to the local DNS servers. > > > > If I run "time host db", I get 0.020 when pointed to an external server, > > I get 1.024 or 1.025 when pointed to 127.0.0.1. > > > > Any ideas what to do to resolve this? > > > > -- > > > > Wayne Walker > > > > wwalker@gnumber.com > > > > Do you care who calls your cell phone at 3 in the morning? > > www.gnumber.com > > > > wwalker@bybent.com Do you use Linux?! > > http://www.bybent.com Get Counted! http://counter.li.org/ > > Perl - http://www.perl.org/ Perl User Groups - http://www.pm.org/ > > Jabber: wwalker@jabber.ntrc.net AIM: lwwalkerbybent > > IRC: wwalker on freenode.net > > > > > > -- Wayne Walker wwalker@gnumber.com Do you care who calls your cell phone at 3 in the morning? www.gnumber.com wwalker@bybent.com Do you use Linux?! http://www.bybent.com Get Counted! http://counter.li.org/ Perl - http://www.perl.org/ Perl User Groups - http://www.pm.org/ Jabber: wwalker@jabber.ntrc.net AIM: lwwalkerbybent IRC: wwalker on freenode.net |