Tag: dns

  • All DNS on the gateway failed for fifteen hours

    One of the two internet gateways lost every DNS lookup for about fifteen hours. Nothing was wrong with the gateway, its network or its resolver software. The root of the DNS had changed its signing key on schedule, and this…

    Read on →

  • Active, and refusing every query

    A routine change to add a forwarding rule took DNS down for the entire lab. Every query from every machine, internal names and external ones alike, came back REFUSED from both resolvers.

    Read on →

  • Six seconds was the evidence

    A certificate was issued in six seconds. That was taken as proof the new certificate provider worked.. It proved the opposite of what it appeared to, and the speed was the tell.

    Read on →

  • Why Unbound

    Every connection to anything starts with a name being turned into an address. In this lab that translation is done by two machines the lab owns, running Unbound, rather than by the internet provider’s resolver or by whatever the router…

    Read on →

  • The step that was not about DNS

    The runbook step was about joining a VPN. One command, on each machine, to enroll it in the private mesh.

    Read on →

  • Every light was green and DNS was dead

    Two new DNS resolvers went live. The configuration validated. Both services reported active. Every internal name resolved correctly, on both machines.

    Read on →

  • Status: the first VMs, and the tier they unblock

    Three virtual machines exist. After weeks of rented gateways and documents, something is finally running on hardware in the building.

    Read on →

  • A clean result from a blindfolded check

    Before running a mail server you check whether your addresses are on email blocklists. A sweep of both gateways against ten lists came back clean on all ten, IPv4 and IPv6, and that went into the record as a finding.

    Read on →