Shows the domains the engine keeps in the DNS precache — regardless of whether there is a queue for them.
The list is set by a file: precached-domains-file in the <dns> block, one domain per line. Entries are refreshed every precached-refresh-interval, 5m by default, instead of by the records’ own lifetime; the limit is precached-max-domains, 500 by default.
When to use it:
| Question | This command or not |
|---|---|
| which domains the node keeps resolved in advance | yes |
| why the first delivery to a domain is slow | partly — whether the domain is in the list |
| what the name server answers now | no — resolve |
# keep large receivers resolved in advance <dns> precached-domains-file /etc/pmta/precached-domains.txt precached-refresh-interval 2m </dns>
1 relation
pmta show precache wc -l /etc/pmta/precached-domains.txt
3 articles
◇What the node tells about itself and through which channelsSeven observation surfaces: the web monitor, the console in four formats, the log, accounting, accounting search, metrics and export to external analytics.◇The watchdog that restarts the engineKeeps an eye on the engine and brings it back up after a crash by itself, sending a crash report to the postmaster address.◇What makes a virtual machine riskyRunning on a virtual machine is possible, but the manual does not recommend it without sufficient hardware and properly tuned hypervisor settings: under load the node may stop responding.