On 05/07/2021, maillists <
list...@nospammail.net> wrote:
> If during a use session any site (re)loading stops, or access to a site
> previously accessed during same use session, unexpectedly returns access
> errors, (sites in question can have been accessed many days ago or just a
> moment ago), if this happens because of server side, firewall or dns lookup
> changes, then I am unable to verify or check if IB actually accesses the
> current, for the site valid ip, meaning it must be a current server problem,
> or if IB tries to access the site using an older now invalid dns result
> in/from its internal, very static and seemingly eternal lasting (within the
> use session) dns cache.
Again, I guess you are in the minority that you leave IBrowse running
long enough for DNS issues to arise :)
> Does anyone have information on how to clear the IB internal dns cache?
It cannot be manually cleared. The DNS cache is not new, by the way -
it has been there since 2.0, and probably in 1.x too. I just increased
it from 64 to 256 entries, since these days, if you have a few tabs
open, it is easy to reach the 64 limit as one site can often access
many different hosts.
I've not looked into the cache logic in great detail, but it looks
like when the cache is full, least used hosts are released.
> Would it be possible to add a menu entry to immediately clear the dns cache,
> so that any page/site reload will force new fresh dns lookups?
>
> Perhaps a configuration option for cache timeout?
Yes, I'll look into this. I did wonder when I extended the cache size,
that perhaps this should be configurable in the settings (this also
means it could be disabled completely, if desired).
> I feel that dns lookups
> today should not seriously add too much of delays on many setups.
Maybe so, but when DNS-over-HTTPS support is available, the internal
DNS cache will certainly remain very useful. Also note that that many
TCP/IP stacks maintain their own built-in DNS cache also.
--
Oliver Roberts / @Futaura /
www.futaura.co.uk