1

TTL optimization set to One Week

Hi,

Can you specify a statement with the duration in cache optimization performance description  (300s if "boost" activated) in the setting tab ? It is not clear.

Is it possible to set TTL to One week or One day with a "super boost" option ?  it’s painful to sort through dozens of redundant and unnecessary requests every day, it’s not normal to have so much DNS traffic in normal daily operations.

Everybody knows how to flush the dns cache on their device or just rebooting their device if there's a major IP change into a parent DNS.

thanks

4 replies

null
    • Xavfree
    • 2 days ago
    • Reported - view

    One day would be a good start (with a warning statement if you want).

     

    https://www.tutoriaux-excalibur.com/threads/augmenter-la-taille-du-cache-dns-sur-iso-windows-11-25h2.41602/

    Sur Windows 11 25H2, le cache DNS est encore plus sollicite par les services de telemetrie IA et Microsoft Store.
    Par rapport a Windows 10, augmenter le MaxCacheTtl sur la 25H2 reduit significativement les micro-pauses de resolution lors de l'utilisation d'applications hybrides web/locales comme Discord ou Steam.

    Augmenter le MaxCacheTtl, c'est donner a ton Windows 25H2 un carnet d'adresses geant pour qu'il n'ait plus besoin de chercher son chemin a chaque carrefour

    • NextDNs
    • 2 days ago
    • Reported - view

    This would break many services.

      • Xavfree
      • 2 days ago
      • Reported - view

       I would really be curious to know which ones, and to be able to experience them for myself. Since Win10, the cache parameter is set by default to 86400s (1 day).

      Can you add this TTL switch parameter to One day for us, in a settings test mode only activable for 24H and one or two times in the month for example ?

      I'm always glad to see a succesful blocked query, but when I see this same query blocked hundred and hundred of times on the day this mean there's a problem somewhere.

      Do you not mind having hundreds and hundred of redundant lines and that this affects your global performance?

      • Xavfree
      • 10 hrs ago
      • Reported - view

       I assume you’re talking about services like "Apple" that constantly check network connectivity by making DNS requests, which is not a very clean way to work because it makes the DNS cache system useless.

      I don't think there are so much services working this way, a "lower TTL option" for those poorly implemented specific web services should do the job.

      Those TTL options would be great, and would give NextDNS users more possibilities to adjust according to their environment.

Content aside

  • 1 Likes
  • 10 hrs agoLast active
  • 4Replies
  • 75Views
  • 2 Following