# cat /etc/bind/named.conf
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";

What's in /etc/bind/named.conf.options, /etc/bind/named.conf.local, and /etc/bind/named.conf.default-zones?

Click to expand...

actually i think i found the problem, the domain i tried to add was already being served by another provider it seem bind decides not to serve it as a result. This conclusion stems from me creating multiple other dns entries that it resolves, i then edit one of those that it responded for to reflect to one i needed and it resulted in it no responding to that query again.

could this be a untold(at least to me) feature of bind to not allow you to become authoritative for a domain that exist somewhere else?
(btw the domain in question will eventually be controlled by my servers, however before this is done my servers will need to be able to resolve for said domain, at this point my domain master will add my ns entries for said domain)

could this be a untold(at least to me) feature of bind to not allow you to become authoritative for a domain that exist somewhere else?

Click to expand...

That'S how it's supposed to be. When you register a domain, you can tell the registrar which nameservers you want to use. These nameserver become the authoritative nameservers for the domain, and it makes no sense to create the zone on other nameservers.