How not to use DNS in DA?

micha

New member
Joined
Nov 23, 2020
Messages
2
My ISP gives me DA and (obviously) I can set up DNS records in DA panel. But I use Cloudflare instead - so I do not care what is actually set on the directadmin DNS page. The domain records there are basicly empty, or have some default junk values.

The problem:
Cloudflare nameservers are set as authoritative for my domain, so everyone in the world gets correct DNS replies from them. Everyone except hosts in my ISP's subnet. They use the junk values from directadmin, because their default nameservers treat the data from Directadmin as source.

Any workaround?
 
My ISP gives me DA and (obviously) I can set up DNS records in DA panel. But I use Cloudflare instead - so I do not care what is actually set on the directadmin DNS page. The domain records there are basicly empty, or have some default junk values.

The problem:
Cloudflare nameservers are set as authoritative for my domain, so everyone in the world gets correct DNS replies from them. Everyone except hosts in my ISP's subnet. They use the junk values from directadmin, because their default nameservers treat the data from Directadmin as source.

Any workaround?
You know what you posted here?:rolleyes:

"They use the junk values from directadmin, "

You can however do some reading the docs and help files for both DA and Cloudflare though.

Search ...
 
Last edited:
Don't use your DA server as DNS resolvers for any of your machines. It's generally a bad idea in any setup. Use resolving-only/recursive nameservers as resolvers. Including on your actual DA server as well (i.e. don't have localhost in /etc/resolv.conf).
 
If you use Cloudflare, just change the Nameserver values in DA to the Cloudflare's for the domain(s), then Bind will look up the CF's records.
 
Back
Top