[Dnsmasq-discuss] Possible to reuse Cache over restats?

[Tobias Hochgürtel]

Hey Dominik,

On 29.06.22, 22:25, "Dominik Derigs" <dl6er at dl6er.de> wrote:
    You could use some widely known and used tools like Wireshark where various
    tutorial are available to see whether the issue is dnsmasq not responding
    or the queries not making their way to dnsmasq or if something happens to
    the queries sent upstream to the forward destionation, or whatever else may
    be happening. We can surely give some assistance here, if you want.

Ah! Yes, absolute true, I will follow your tip to analyse it and provide more information when I have them. Thanks for the hint to Wireshark, and how and what I have to analyse. I will increase the logging of dnsmasq, and log again to a file instead only to stdout. 

On 29.06.22, 22:25, "Dominik Derigs" <dl6er at dl6er.de> wrote:
  There is no such feature and there is also nothing planned at the moment
  (not that I'd be aware of).

Would such a feature make sense? I thought like this: that when I have the DNS Name and IP's here in my local network, everything goes faster, and I think that a DNS changes his IP Address also doesn't happen often, so it would be interesting to just store them and reuse them over a restart or move them from one system to another.

Or is it so that DomainName and their IP Address often / frequently changes? I have some domains like Hochguertel.work, and I not really changing my IPV4 and IPV6 addresses there.


I hope the way how I replay is correct for a mailing list, I copied the behavior from Dominik how he replied to me. I'm new, if there is a fancy, guide how to work with a mailing list I'm open to read it.

Best, 
Tobias

On 29.06.22, 22:25, "Dominik Derigs" <dl6er at dl6er.de> wrote:

    Hey Tobias,
    
    On Wed, 2022-06-29 at 18:37 +0000, Tobias Hochgürtel wrote:
    > There isn't a feature to reuse the dns-cache?
    > or a plan to add this feature?
    > 
    
    There is no such feature and there is also nothing planned at the moment
    (not that I'd be aware of).
    
    However, restarting dnsmasq once per hour surely is the least optimal
    solution to circumvent what you are observing.
    
    On Wed, 2022-06-29 at 18:37 +0000, Tobias Hochgürtel wrote:
    > I also don't know how I can analyse that behavior.
    
    You could use some widely known and used tools like Wireshark where various
    tutorial are available to see whether the issue is dnsmasq not responding
    or the queries not making their way to dnsmasq or if something happens to
    the queries sent upstream to the forward destionation, or whatever else may
    be happening. We can surely give some assistance here, if you want.
    
    Best,
    Dominik