On 28.05.24 20:21, Roberto CORRADO wrote:
is advisable to set dns-expire a 3600 sec instead 1Day (86400)
for dynamic IP connection?
I wouldn't want to be one day out of usenet :-)
thank you all for the support
dns-expire is a global value, not per peer value and setting it on your
side (if you have dynamic ip) would not change anything.
inn uses the underlying dns servers to resolv names, so it should honor
the dns records expiry value?
your dns is set to 600 which should be fine...
if inn honors the dnsexpiry and does not overwrite it with 'dns-expire'?
dig a news.corradoroberto.it
;; ANSWER SECTION:
news.corradoroberto.it. 600 IN CNAME corradoroberto.it. corradoroberto.it. 240 IN A 130.25.86.223
https://www.eyrie.org/~eagle/software/inn/docs-2.7/innfeed.conf.html
GLOBAL VALUES
The following listing show all the keys that apply to the process as whole.
...
dns-retry
This key requires a positive integer value and defaults to 900. It
defines the number of seconds between attempts to re-lookup host
information that previously failed to be resolved.
dns-expire
This key requires a positive integer value and defaults to 86400. It
defines the number of seconds between refreshes of name to address DNS translation. This is so long-running processes do not get stuck with
stale data, should peer IP addresses change.
^^ i'm not sure how to understand the last sentence:
" This is so long-running processes do not get stuck with stale data,
should peer IP addresses change. "
if peer address changed but internal cache? still has it, it is useless
and somehow stale too?
--
.......
Billy G. (go-while)
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)