I am rather curious if NethServer 8 included DNS will in futute also support CNAMES for any host, not only the NethServer itself.
Nethserver 7 only allows CNAMES for the NethServer, not any other host.
If CNAMES are not possible, one is forced to create an A record, creating a second PTR for the same host, but with a “wrong” name! The more CNAMES needed, the more it becomes useless, at least for monitoring.
A DNS with 2 or more PTRs for the same host is either badly set up - or not really usable!
Some people are not aware of the fact that in most OS one can enter in several DNS servers, Windows Workstations support 3.
But, as long as the first DNS is working, the other DNS will NEVER be queried, even if they could provide the sought answer.
Well by now the only DNS server software included in NS8 is the Samba built-in DNS and that’s not managed automatically: existing modules do not need an internal DNS service to run. ATM DNS is only a service provided by someone else.
Creating a DNS module for NS8 shouldn’t be too difficult though. Of course it would conflict with Samba DC on port 53, so they can’t live on the same node. I think that’s not a big issue because a NS8 system manages also multiple nodes.
What I’d consider an interesting development is integrating the DNS management in the NS8 core, and fully automating it. Not only to integrate and manage an internal DNS module but also external and public DNS providers, through their APIs. This could be a future goal for our project, I mean something to work on after we reach a stable release.
Edit: this is a related card added one year ago to the project board: Trello
actually the developers were contemplating a built-in DNS, meaning one built into NS itself, weather this is achieved by building from scratch, or from taking an existing one and building on top of it, or customizing and help improve an existing one, all these are options.
Now when it comes to software Development @Andy_Wismer all available options and alternatives become a basis for building a knowledge graph for utilization when a software development implementation will take place. No developer wants to re-invent the wheel.
As i said, sharing is caring, you might not like the option, someone else might come across it and it helps them in one way or another.
I know for sure you will never use a free hosted DNS service, but someone else might want one, especially one that integrates with self hosted thingies…
I for one use Cloudns and Bunny DNS, i would love cloudflare, but the features i need from them are in a pricing plan i cant afford.
Also, i don’t self host DNS for many of my core, used to, not anymore, because i cant achieve a proper cluster to prevent complete failure, i guess not enough experience, or not enough resources to put that to function.
Create an account.
Create a domain - the same one like the one you use at your regular registrar
Create the same records as the ones you use at your regular registrar
*** At the bottom of the records take the 2 names of the nameservers
Go to your regular registrar and change the nameservers for the ones given by Cloudflare.
Voilà, it works after a few minutes if your regular registrar is fast to propagate the change.