DNS

Find dns records in order to identify the Internet footprint of an organization. Recon that enables deeper security assessments and discovery of the attack surface.

dnscrypt-proxy 2 - A flexible DNS proxy, with support for encrypted DNS protocols. - Cloaking · DNSCrypt/dnscrypt-proxy Wiki

Getting rid of EKS DNS issues at scale

Using node local caching on your Kubernetes nodes to reduce CoreDNS traffic

We faced a network disconnection from our instance that lasted for a few seconds less than 1 minute Driver info Jul 12 07:08:09 docker-linux kernel: [20045236.927756] ena: Elastic Network Adapter (...

CoreDNS 1.5.

This page provides hints on diagnosing DNS problems. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

Overview I was playing around with my home Kubernetes cluster and decided to try out Node Local DNS Cache. It’s a really cool piece of software, that helps with DNS load by caching most of responses on the node local DNS and solves Linux conntrack races, which cause intermittent delays of 5s for some DNS … Continue reading Kubernetes Node Local DNS Cache →

In this post, I'll talk about how I learnt about FQDN, Search Paths and ndots to tackle slow DNS resolution in Kubernetes

A frequent complaint expressed on a certain website about Alpine is related to the deficiencies regarding the musl DNS resolver when querying large zones. In response, it is usually mentioned that …

I recently ran into a weird issue after switching an application’s container base image from Debian to Alpine Linux. Things worked out fine in staging and sandbox environments, but suddenly in production (of course!) the application failed to resolve a service it needs to talk to.

Due to the client-server architecture of DNS, properly working DNS name resolution on a system is almost always dependent on not only the proper configuration and operation of DNS on that system but also on that of its resolving nameserver and the many authoritative nameservers used to resolve its DNS requests. Since DNS is a distributed directory, recursive name resolution often involves numerous behind-the-scenes interactions with many different authoritative nameservers. These numerous interactions create many possible points for failure.

A couple of weeks ago I took a spare RaspberryPi 3 leftover from my old k3s cluster and installed OpenBSD on it using...