6 ms·
> I prefer to run my own local recursive resolver. Used to be fine. I stopped doing it when average TTL dropped to 300 seconds and it takes far too long for my
by winstonwinston 12d ago
> I prefer to run my own local recursive resolver.
Used to be fine. I stopped doing it when average TTL dropped to 300 seconds and it takes far too long for my local recursor to get the answer >100ms, when 3rd party resolver delivers in <10ms.
- pocksuppet 12d agoYou don't have to obey TTL. You can use Unbound options like: cache-min-ttl: 3600 // seconds cache-min-negative-ttl: 3600 // seconds or serve-expired: yes serve-expired-client-timeout: 20 // milliseconds to wait for resolution before serving the old value to the client
- clownstrikelol 12d agoCan also have unbound preemptively refresh cached values too... prefetch: yes Tada, now your unbound serves records faster than the round trip out to anything off your own network in most cases.
- bigstrat2003 12d agoIt's still fine. I run my own recursive resolver and have no noticeable issues.
- tosti 12d agoGood for you