Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Other modules / Re: error save dns module
« on: August 11, 2018, 03:13:25 pm »
Hi All!
It seems to me the DNS implementation in Zentyal 5.1 is somehow completely broken. I tried to figure out what is wrong but encountered such a baffling amount of perl scripting and other shenanigans that I decided to abandon Zentyal. The easiness of setting up an AD Domain Controller is cool, but the forced integration of a not working DNS concept vexes me. Why do I even have to have the Zentyal server as the DNS server for my DNS domain? I have a plain vanilla bind9 on another box and would expect to just enter the name server information into the Zentyal configuration somewhere and be done.
Probably I am doing something wrong on the design level, but it all worked wonderfully up to the Zentyal 4.1 installation I ran the last 2 years. Suddenly after upgrading to 5.1 I can no longer work with the AD Domain and all error messages on various devices (mainly timeouts when accessing LDAP or Kerberos) point to the fact that name resolution and/or reverse lookup does no longer work on the Zentyal machine.
I spent hours now trying to figure it all out - from now on I will spend the time getting rid of that woeful Microsoft crap alltogether and either revert to local user management on all my devices or check out some LDAP server concepts.
Sorry to be such a whiner, but I need to vent my frustration somehow :-)
Regards and bye,
Loderunner
It seems to me the DNS implementation in Zentyal 5.1 is somehow completely broken. I tried to figure out what is wrong but encountered such a baffling amount of perl scripting and other shenanigans that I decided to abandon Zentyal. The easiness of setting up an AD Domain Controller is cool, but the forced integration of a not working DNS concept vexes me. Why do I even have to have the Zentyal server as the DNS server for my DNS domain? I have a plain vanilla bind9 on another box and would expect to just enter the name server information into the Zentyal configuration somewhere and be done.
Probably I am doing something wrong on the design level, but it all worked wonderfully up to the Zentyal 4.1 installation I ran the last 2 years. Suddenly after upgrading to 5.1 I can no longer work with the AD Domain and all error messages on various devices (mainly timeouts when accessing LDAP or Kerberos) point to the fact that name resolution and/or reverse lookup does no longer work on the Zentyal machine.
I spent hours now trying to figure it all out - from now on I will spend the time getting rid of that woeful Microsoft crap alltogether and either revert to local user management on all my devices or check out some LDAP server concepts.
Sorry to be such a whiner, but I need to vent my frustration somehow :-)
Regards and bye,
Loderunner
2
Other modules / Re: error save dns module
« on: August 11, 2018, 11:57:30 am »
Hi!
Thanks for the fast reply! The solution did work in principle, but now I got stuck with an even more complex error. I guess I will just reinstall from scratch, should not be that hard for my tiny home environment.
Thanks again and have a nice time!
Loderunner
Thanks for the fast reply! The solution did work in principle, but now I got stuck with an even more complex error. I guess I will just reinstall from scratch, should not be that hard for my tiny home environment.
Thanks again and have a nice time!
Loderunner
3
Other modules / Re: error save dns module
« on: August 11, 2018, 03:09:48 am »
Hello paimcoop,
I got the same problem ... which results in my Zentyal machine being unable to resolve hostnames :-(
Unfortunately I have no solution either. Hoping for some help here ...
Regards,
Loderunner
I got the same problem ... which results in my Zentyal machine being unable to resolve hostnames :-(
Unfortunately I have no solution either. Hoping for some help here ...
Regards,
Loderunner
Pages: [1]