It can work as a full DNS, but you may need to manually create entries (forward and reverse lookup).
In a windows domain environment, you'll always need to have a Windows based DNS for internal resolution. AD requires a ton of custom entries, such as ldap, gc, kerberos, etc...gets even more complex if you use Exchange.) that just don't lend themselves to 3rd party DNS solutions. And If you get something wrong, AD breaks big-time.
Astaro is best used as a DNS proxy between your windows DNS and DNS servers on the internet in your situation.
__________________ ACE v8/SCA v9.3
...still have a v5 install disk in a box somewhere.
It can work as a full DNS, but you may need to manually create entries (forward and reverse lookup).
In a windows domain environment, you'll always need to have a Windows based DNS for internal resolution. AD requires a ton of custom entries, such as ldap, gc, kerberos, etc...gets even more complex if you use Exchange.) that just don't lend themselves to 3rd party DNS solutions. And If you get something wrong, AD breaks big-time.
Astaro is best used as a DNS proxy between your windows DNS and DNS servers on the internet in your situation.
I found several threads where users reported problems with the dns or they had problems to configure reverse resolving.
Still the same question: What features are you missing on the ASG?
And for the whole rest it works fine [;)]
ok
I will give astaro a chance.
Do you ve a link for an example or a tutorioal how how to configure the dns so that it is working for resolving internal systems and answering requests about exernal adresses? The config seems to be simply by the webinterface but it is realy simple to block a feature by a wrong rule or somethin else.
