No this wont work.
This way NS is just a “forwarder” but for queries from lan.
there are two components for DNS in Nethserver.
1 is the DNS query (upstream so to speak)
2 are the DNS entries for what Nethserver is responsable ( this is the part that you are intersted in)
The first part is the same DNS setting that you will find in home router.
This tels to the NethServer to send queries to a nother NameServer.
if you take this example you will see the logic.
( NameServer for md.com) -----> ( Nethserver "who is md.com ?") ----> let's ask NameServer for md.com ---|
^--------------------------------------------------------------------------------------------------1 You declare the domain in the NS.md.com. and tell that “x” Ip is for that domain (ok for now)
2 Ip “x” is directing to Nethserver. (ok for now)
3 Nethserver is set up to ask for name resolution for the Domain MD.com to the NameServer NS.md.com (Not OK !)
it goes back again to the Nameserver of domain MD.com server because he does not know about domain MD.com !
so basically you have NethServer ask again the Nameserver. You create a loop.
Question:
Why you do not want to set up DNS on Nethserver to solve the md.com and other domains ??
You are making all sorts of tricks, to resolve DNS queries and jump trough a lot of hoops to solve something that in the end will be just a manual DNS solver? (if it works…)