What kind of response do you get from the slave servers if you query them directly (using eg dig)?

check out the updated question with dig

That doesn't look like a representative query for the problem you were describing. Something like dig @162.159.27.72 example.com +norec, maybe?

check now question updated

I want to Use Linode’s DNS Manager as a Slave, on debian the file is "named.conf.options" and I did check with named-checkconf, I get nothing back

In the earlier version of the question where you had the dig output for a regular query we could see that you get SERVFAIL back which suggests that the zone exists but something is wrong. Quite possibly they are unable to perform the zone transfer. Can you check and double-check that you have given them the correct information about your zone (ie, correct master ip and obviously correct zone name) and check your own logs for traces of their attempted zone transfers?

when you say them do you mean linode or registrar? I have access to bind server

Do I need to add A record at my DNS for ns1.linode.com ns2.linode.com ns3.linode.com ns4.linode.com ns5.linode.com

I meant the operator of the slave servers (Linode in this case, if I understand correctly)

yes I added the correct Slave Zone at linode DNS manager

As in that it was already correct? Unless you mean that you just fixed something and it now works, clearly something is wrong either on your end or on their end. What about your logs, any hints as to what happens to their zone transfers?

this is what I have at linode dns manager

imgur.com/a/JM3MC0s

and I don't see any errors on my server

when you look at this document, do you see anything amiss? linode.com/docs/websites/cms/set-up-dns-services-on-cpanel

I doubt you need anything in "domain transfers" in the Linode zone configuration, but I guess that doesn't hurt

What do you see in the logs?

Regardless if it's an error or not, anything at all regarding the expected zone transfers?

Okay, but where from was that initiated? And was that source allowed?

on my server

Ok, but I don't believe your server is supposed to be allowed (at least not with the config included in the question)?

Regarding what you did... dig axfr @162.159.25.129 revelhost.net (?), I'm not actually sure how that is relevant to anything

That was you trying to axfr from one of the linode nameservers. Not the other way around, right?

It's the other way around that you are trying to get to work

Correct?

The delegation is important in the greater picture but not actually relevant to making the zone transfer work

I would still suggest checking the logs for AXFR attempts from the Linode nameservers. They should be attempting and based on them answering queries with SERVFAIL it would appear they fail to complete the AXFR

these are the dns errors intodns.com/revelhost.net

I dont know if this has anything to do with it, but I also Register a new Name Server at enom ( ns1.revelhost.net and ns2.revelhost.net) pointing to my main ip

If the question is about the zone transfers to the Linode nameservers, then it doesn't have to do with it. If it has to do with anything else, then it could possibly be relevant but then I'm not sure what the question actually is.

it wasn

But what do your named logs say?

nt a question

where are the named logs?

Something like journalctl -ex -u bind9 maybe, unless you have specifically configured something.

client 104.237.137.10#45797 (revelhost.net): zone transfer 'revelhost.net/AXFR/IN' denied

Well, there you go

why is it denied?

So that is one of the IPs listed by Linode, and which the small part of the named config you have shown suggests would be allowed, but for whatever reason it's actually denied. If you are sure that named has been reloaded/restarted after you made those changes, I think you'll have to show what is actually going on in that named config as a whole.

Eg, do you also have allow-transfer on the zone level, overriding the global configuration that you are showing in the question?

in debian you have /etc/bind/named.conf.options

Sure

and /etc/bind/named.conf

Yes...?

And named.conf.local and whatever

(Worth noting, named itself only knows to read /etc/bind/named.conf, the file Debian ships just has include directives pointing to those other files so it reads them all)

will this restart my named server

killall -HUP named

systemctl restart bind9 would be the more general approach to restarting a service in modern Debian, I guess. But sending HUP ought to work for getting it to reread the config.

facepalm

I guess thats whats stoping it

Yes

If that is the relevant zone / if the relevant zone looks the same

(I think it was revelhost.net earlier?)

I have more than one domain, I only do it for this one?

yes

Well, you were talking about revelhost.net before, and if that also has allow-transfer none, then that certainly explains why what you asked about doesn't work

If there are more domains that you are setting up the same way, I guess you'll want to fix all of them

Not saying this to cause offense, but I do get the feeling that from a professional perspective you're in over your head and that unless this is purely for learning purposes you may want to use some managed service instead. Just my 2c.

I think I got it

not exactly, I'm a web designer, however i'm new to dev-ops

I prefer to manage my own, more control

I certainlly will not use shared hosting

thanks for the help

"More control", but you seem a bit unfamiliar with the whole environment. As long as you are prepared to learn, I guess.