First of all, you do realize that you can't change the directadmin nameservers, right?
Worry about your own nameservers, not those for DirectAdmin.
The danger is very overrated.
You can change your own nameservers if you want to make them non-authoritative.
If you do you'll have to make sure you don't have localhost or your own IP#s in your /etc/resolv.conf.
You'll have to use other nameservers (perhaps from your connectivity provider) in your /etc/resolv.conf file, or your own server won't be able to do lookups anymore. Which means among other things that it won't be able to send email.
This is a new
item that
DNS Report has just started incorporating, but it's NOT a new issue; it's been around since BIND was first written, since it's capable of being authoritative as well as caching, at the same time. And people have used it for both at the same time.
If your upstream offers you recursive (caching) DNS servers and if you set up your servers to use them, then you can make yours non-authoritative.
Some of our machines have non-caching nameservers, and others don't, and now that
DNS Report is reporting it as a problem we're going to have to make them all non-caching.
But don't rush into it without planning your connectivity of all your servers to available caching-nameservers on their local network.
Jeff
