Knot Resolver 6 News: Improved Garbage Collection and Prefetch

The process of resolving a client query may require multiple requests to different authoritative name servers. We store their answers in our cache to speed up processing of future queries. For cache management, we use garbage collector to evict the least useful records in case of space exhaustion and prefetch to proactively update the most useful expiring ones. In this post, we describe how the classification of usefulness of the records works in the next Knot Resolver version 6.6.0 and how it differs to earlier implementation and show the impact of the changes to the latency of processing client queries on the results of measurements.

27.10.2026 at 10:15 Počet komentářů 0
Share on

SaltStack, DNS and ssh

In my last post, I showed, how we can combine SaltStack and Knot to have some basic records filled in your zone. As I was introducing the concept, I picked the most obvious and basic entries. But since we have a hammer now, everything starts to look like a nail. And there is much more that can be stored in DNS apart from IP addresses. Let’s take a look at some other examples and how to get them automatically filled in by SaltStack.

31.1.2024 at 9:20 Počet komentářů 0
Share on

Managing DNS via SaltStack

Running services online without domain is hard. More services you run, more DNS entries you need to manage. More services you run, more servers you need to manage. And when you manage several servers, it’s time to use some orchestration. But what about all those domains associated with those servers and services? Can’t that be also part of the orchestration? Somehow automated? Of course it can. Let me tell you how am I handling it for my domains and servers.

16.1.2024 at 14:00 Počet komentářů 0
Share on

RFC 9432: DNS Catalog zones

A DNS zone is usually served by multiple authoritative servers, which is actually recommended for the sake of redundancy. Large authoritative DNS operators even combine different name server implementations to avoid complete infrastructure outage in case of any software error. For synchronizing zone contents between authoritative servers, a DNS-specific mechanism is available, called zone transfer. It is well established and supported by all common DNS implementations. It enables both full zone transfer (AXFR) and incremental update (IXFR).

 

25.7.2023 at 11:30 Počet komentářů 0
Share on

DNS traffic collector

We are releasing dns-collector, an entry part of our pipeline for monitoring of our DNS servers and analysis of the DNS traffic. Together with advanced analysis of the collected data, we can not only monitor the DNS traffic for urgent problems, but also detect and examine long-term trends and issues (e.g. misconfiguration of other servers). We have presented this system at the IT 15.2 conference (video and slides in Czech).

27.6.2018 at 9:45 Počet komentářů 0
Share on