• external DNS: Ignore Ingress object

    1 min read

    If we are using external DNS to create DNS records based on the configured Ingress objects we might face a situation where we have two Ingress objects with the same hosts configured:

    $ kubectl get ingress
    NAME                    CLASS    HOSTS                                          ADDRESS       PORTS     AGE
    repo-nginx              <none>   repo.pet2cattle.com                     80        194d
    repo-alb                <none>   repo.pet2cattle.com                     80, 443   115d

    In a situation like this, we want to be able to tell external DNS to ignore one of them.


  • Install and configure external-DNS on AWS EKS

    3 min read

    With external DNS the DNS records for the ingress objects we have will be created automatically. We can choose between several cloud providers but we can even configure it to use the standard dynamic zone manipulation defined in RFC-2136. Let's see how to configure it on AWS EKS with Route53


  • tcpdump: filter DNS queries

    2 min read

    When a DNS change is involved in an ongoing issue, we need to be sure when we use, for example curl, whether we are hitting the new or the old resource. Is that DNS record still cached locally? One of the best ways of checking this is by sniffing the DNS traffic using tcpdump



From pet to cattle
Treat your kubernetes clusters like cattle, not pets
tags related to this category