Can I give specific users/domains a different external NS? (not DA's)

[barryke]

My server hosts a DNS NS (by DA) and my datacenter/hoster runs a DNS NS (TransIP.nl).

Is there a possibility to specify certains users/domains to use a non-DA nameserver (NS) to resolve DNS records ?
Example is the website wants to send email, and may query the incorrect NS: local DA instead of datacenter hoster's NS.
It is possible I have overlooked the settings for users/domains, since I've yet to get accustomed to the new UI skin.

I read documentation like https://docs.directadmin.com/other-...-to-run-dns-services-on-my-directadmin-server
But I cannot find the solution to this question.

PS. setting DA's NS as NS1 is possible, but then i'd to add another IP (or DA multi-server) because NS2 is required also.

 

[Richard G]

Just use DA's default ip if you only have one, you can use this for ns1 and ns2 because that is only used locally.

If you are really using your own nameservers on DA, then you need 2 diffent ip's at least and I think transip even requires different subnets/locations.

Resellers can use their own nameservers or sometimes also use DA's nameservers ip's as nameserver.

Example is the website wants to send email, and may query the incorrect NS: local DA instead of datacenter hoster's NS.

That's odd. If a user wants to send mail, he normally contacts your server.
If you use the DNS of transip as nameservers, then you have to copy all information from DA to that domains DNS in transip.

For example.
mail.domain.com 192.168.0.10 in DA, should be copied with the same ip to the DNS of domain.com in Transip.

You can also send me a pm then we can talk in Dutch that makes things a lot easier probably.
However, next answer of me will be tomorrow as I'm going to watch TV now.

P.s. if you find the Enhanced skind easier to setup things. Then switch to enhanced skin, set things up as you're used to, and then switch back to Evo and see how it looks there. Makes learning Evo also easier.
I myself keep working mostly in Enhanced because that's easier/clearer. Could also because I'm too used to that skin. But I always even liked it better than the cPanel skin, which is kind of Evo grid skin looking.

 

[barryke]

See next post for ontopic continuation, this post explains why I am looking to allow domains/users to use external NS.

Yes that would work.. but let me explain the situation. In the past I used DA DNS and was happy with it. I had NS replication setup from DA to hoster NS (then CloudVPS) and it allowed my users to do their DNS MX updates whenever. Best thing was: it was all part of a backup.

<rant>
However - when the CloudVPS company got acquired by TransIP they just deleted all that (without consulting me) an put a copy of DNS records in their own NS. Yes the hoster broke the DA DNS of my servers. Customers have no way to adjust their own MX records etcetera. TransIP support is responsive but not helpful and willing in restoring this situation.
</rant>

So yes for now I avoid the TransIP NS and setup DA to be the NS, if I add more NS servers or add IPs as a workaround. TransIP does not want that.

I shall return to the above topic in the future, because I want my users to do their own MX updates within DA, and have all DNS backed up within the users as an atomic whole. The TransIP NS does not add value for me.

 

[Richard G]

TransIP does not want that.

Transip has nothing to say about that. In fact they shouldn't even have crippled things for you.
Users in DA can always change their own MX page if you have your own nameservers running.

There are others here who also use Transip and have their own nameservers running in DA too. However, you can also choose something like Cloudflare for external DNS.

 

[zEitEr]

Hello,

Example is the website wants to send email, and may query the incorrect NS: local DA instead of datacenter hoster's NS.

It may happen if you got nameserver 127.0.0.1 in /etc/resolf.conf on the top of the list of nameservers, and locally hosted DNS records are not in sync with remove (authoritative) nameservers. If this is the case, then you will need either to sync DNS zones or remove nameserver 127.0.0.1 from /etc/resolf.conf