Checking DNS servers regularly Identifying DNS probes Analyzing DNS activity
Checking DNS servers regularly Identifying DNS probes Analyzing DNS activity
You're encountering random IP addresses in your DNS records for specific domains. This usually happens when DNS responses include additional data like TXT records or when misconfigurations are present. Using DNSmaq can help manage and filter these entries effectively.
Concealing your DNS server details from potential discoverers. Running bind9 is the setup.
I'm setting up a DNS server, thinking about BIND and what PiHole includes. PiHole relies on dnsmasq, but it doesn't seem to offer a way to hide version details during setup—only a choice you set at compile time. If you keep things current, you shouldn't face major issues. If not, outdated versions could weaken your security. Assuming you don’t need to rebuild dnsmasq, you might restrict access to port 53 only from your home network or ISP ranges. With a single static address, it’s straightforward. For dynamic IPs or mobile use, managing all possible addresses becomes complex. Another way to boost security is running the service on a non-standard port, though that’s not necessary here. They’re actively checking for outdated, vulnerable DNS tools. If you’re current, everything should be safe.