On Tue, Sep 09, 2014 at 08:20:48PM +0200, bert hubert wrote: > On Tue, Sep 09, 2014 at 05:57:08PM +0000, Todd Smith wrote: > > > Actually that begs one more question--as of right now I actually have > > network-timeout set to 5000 in recursor.conf, yet obviously it's still > > timing out considerably sooner than that; is there, say, some other > > setting (that is, of course, within PowerDNS) that might be conflicting > > with this causing it time out sooner? > > Just just checked, 3.6.0 honors network-timeout correctly under normal > conditions, seeing if there are possibilities when we might be short > circuiting it.
Ok, this has to do with the nature of trace-regex, which outputs the whole thing at the end of the resolve process, with only one timestamp. Clarified the output a bit to: Sep 09 20:28:50 [13281] toyotasupplier.com.: Resolved 'toyotasupplier.com.' NS gslb-ns1.toyota-na.com. to: 63.238.139.235 Sep 09 20:28:50 [13281] toyotasupplier.com.: Trying IP 63.238.139.235:53, asking 'toyotasupplier.com.|MX' Sep 09 20:28:50 [13281] toyotasupplier.com.: timeout resolving after 5000.47msec Sep 09 20:28:50 [13281] toyotasupplier.com.: Trying to resolve NS 'gslb-ns2.toyota-na.com.' (2/2) https://github.com/PowerDNS/pdns/commit/863ca18dd298ad0f2ee377aaf539450bc81e0b0a I also get intermittent failures of toyotasupplier.com here by the way, so it isn't just you! Bert _______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
