New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different zones on DNS servers #296

cahluor opened this Issue Mar 22, 2016 · 4 comments


None yet
2 participants

cahluor commented Mar 22, 2016


I have a setup where I manage different groups of nameservers with differents zones.
Is it possible to have a group of zones existings on a group of servers and another set on another group ?


This comment has been minimized.


WillyXJ commented Mar 22, 2016

Absolutely! You can create your server groups through Config -> Servers and click on the Server Groups link in the upper right. Once you've defined your server groups, you can define which group(s) and/or server(s) each zone is hosted on in the Zones page. This can be done when adding new zones or editing the zone properties of existing zones.


Of course, you are not required to create server groups, but they may make it easier to manage your zones.


This comment has been minimized.

cahluor commented Mar 23, 2016

Ok thanks, Exactly what I was looking for... but failed to see it because I use template and in this case the options are masked.

If I remove the template and assign the zones to "internal servers" it works.

I tried to change it on the template level. I put the template "internal" to the group "Internal servers" but it don't seems to work.

I just add a look in classes/class_buildconf.php the funcion buildZoneConfig look for the field "domain_name_servers" which always "0" when you use a template, so the zone exist for all servers.

@WillyXJ WillyXJ added this to the 2.x bug fixes milestone Mar 23, 2016


This comment has been minimized.


WillyXJ commented Mar 23, 2016

Thanks for the report. Server selection within the templates should be honored. I have verified they are not. I'll work on a bug fix for this.


This comment has been minimized.


WillyXJ commented Mar 25, 2016

This is fixed in fmDNS v2.1.8.

@WillyXJ WillyXJ closed this Mar 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment