

I don’t know how the others set theirs up, but I use “views” in bind 9 https://kb.isc.org/docs/aa-00851
Essentially, the DNS I run on a router-like box much like you describe uses a different database depending on whether you query from an internal IP address or a public address. For me, the advantages are that I can let devices on my local network declare their own names to DHCP and enter them in DNS without worrying about the outside world. Mu internal network doesn’t crash if my ISP changes my address, Certbot happily requests certs for any site with a public address, and that cert works seamlessly on the corresponding internal address, no wildcards or DNS challenge required.


It’s really not the publicly disclosed vulnerabilities you need to worry about. Most of those vulnerabilities have existed for years - the recent php thing is supposedly 12 years old. Maybe someone’s been out there exploiting it for 12 years.
The people who have sought and exploited vulnerabilities since computers went online don’t disclose what they find. They are the people who should be most worried about AI-assisted vulnerability research, because it directly attacks their business model.