Skip to content
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

6.1 Broke new DNS entries #1925

burkeazbill opened this issue Dec 2, 2019 · 4 comments


Copy link

@burkeazbill burkeazbill commented Dec 2, 2019

Describe the bug
Prior to the 6.1 release, using the Zentyal web interface to add a new DNS entry resulted in being able to resolve entries. Now, the entry is added to the web ui, but NOT added to the actual zone file (have only tested/verified with AD integrated zone).

To Reproduce
Steps to reproduce the behavior:

  1. Go to DNS
  2. Add new host entry with valid IP
  3. Save changes
  4. Attempt to resolve newly added entry with ping or nslookup
  5. Attempt to reverse lookup the newly added entry with nslookup

Expected behavior
ping and/or nslookup should result in a valid response for the newly added entry


Zentyal OS (please complete the following information):

  • Version: [6.1]
  • Version of the module which has the bug [DNS]
  • Modules installed [Network, Firewall, DNS, FTP, Logs, NTP, DC, Mail, SOGo Webmail]

Other OS (please complete the following information):

Additional context
Unanswered forum threads regarding this issue from multiple users:,34771.msg113042.html,34752.0.html


This comment has been minimized.

Copy link

@Neustradamus Neustradamus commented Dec 5, 2019

@burkeazbill: It is solved now?


This comment has been minimized.

Copy link

@burkeazbill burkeazbill commented Dec 6, 2019

@Neustradamus - I have not had an opportunity to check the 6.1.1 ... It seems that brunolorente closed this and linked a change.. I don't see how/why that change would resolve this issue. I had to re-deploy 6.0 and will NOT upgrade without a pre-upgrade Snapshot (VMware) of the VM running this.


This comment has been minimized.

Copy link

@sat-dish sat-dish commented Dec 6, 2019

Changing "allow_duplicated_ips = yes" does not fix this issue. You still can not resolve new DNS entries, but it does fix the #1920 issue.
Maybe @brunolorente can elaborate on what semmantic versioning change was made?
I downloaded this as a replacement for Microsoft AD last week and have been banging my head against the wall trying to figure out why this wasn't working. I'm either going to downgrade and start over with my config and follow @burkeazbill suggestion of a snapshot before upgrading, or bite the bullet and purchase Server 2016 as this bug is a showstopper for me.


This comment has been minimized.

Copy link

@Neustradamus Neustradamus commented Dec 6, 2019

@burkeazbill: Thanks for your reply!
@sat-dish: We are okay, it is for this that I have done my comment ^^
Several times, tickets are closed before the solution, it is not good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.