30 Jul
2019
30 Jul
'19
6:41 p.m.
I tend to run 3600 on the soa and 600 or less on the host records. Long
lived caches are only really useful if you have a DNS server behind a high
latency link where a 300+ms rtt makes for time to first byte feel
extreamly slow while you wait for name relsolution. I think a pi can
handle 25+mb/s of DNS traffic without breaking a sweat (provided you dont
have aggressive logging enabled)
On Tue., Jul. 30, 2019, 15:24 Ian McLaughlin via 44Net, <
44net(a)mailman.ampr.org> wrote:
Server load? DNS queries are tiny and require
virtually zero processing -
all served out of RAM for the most part. Google recommends a TTL of 3600
(1 hour) here:
https://support.google.com/a/answer/48090?hl=en
The advantage of a short TTL far outweighs the ‘load’ created by increased
queries today.
Ian VE7BST
On Jul 30, 2019, at 3:16 PM, Bradley Parker via
44Net <
44net(a)mailman.ampr.org> wrote:
It shouldn't be such a short TTL..... Caching helps reduce server load.
On Tue, Jul 30, 2019, 12:49 PM Rob Janssen via 44Net <
44net(a)mailman.ampr.org>
wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
It
*should* be a multi-step process:
Why so difficult? The TTL in the ampr.org zone is one hour, and it has
been for a long time.
Rob
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net