if you may, we can also go on in German, maybe this clears things up (especially given the fact that Kai from all I know is also a German native speaker).
As for the DNS services within the Astaro, there are some limitations on what you can and cannot do with it.
First and foremost: the Astaro is - as Scott has pointed out - not a replacement for a full featured DNS server. There are key things missing, e.g. the opportunity to publish other records that are neither A nor PTR records in the box itself.
It also lacks the opportunity to support the AD / Microsoft built in DNS update mechanism that automatically keeps track of DHCP leases as they're handed out dynamically and maps them to the matching DNS name for your AD host.
So, no, especially if you run a Microsoft shop you can't and shouldn't replace the internal DNS services with the ASG completely. What works for most of the customers I deal with is to use Request Routing and still use the Astaro as their main DNS server.
And again: if you lack a feature such as "make the Astaro able to host public DNS zones with MX records, bells and whistles" that's probably a bigger feature request.
What would probably work and would add little overhead was the possibility to specify the Astaro as a DNS proxy for public zones, using a combination of request routing and allowing all clients, not only the ones specified for recursive requests to query those zones.
if you may, we can also go on in German, maybe this clears things up (especially given the fact that Kai from all I know is also a German native speaker).
As for the DNS services within the Astaro, there are some limitations on what you can and cannot do with it.
First and foremost: the Astaro is - as Scott has pointed out - not a replacement for a full featured DNS server. There are key things missing, e.g. the opportunity to publish other records that are neither A nor PTR records in the box itself.
It also lacks the opportunity to support the AD / Microsoft built in DNS update mechanism that automatically keeps track of DHCP leases as they're handed out dynamically and maps them to the matching DNS name for your AD host.
So, no, especially if you run a Microsoft shop you can't and shouldn't replace the internal DNS services with the ASG completely. What works for most of the customers I deal with is to use Request Routing and still use the Astaro as their main DNS server.
And again: if you lack a feature such as "make the Astaro able to host public DNS zones with MX records, bells and whistles" that's probably a bigger feature request.
What would probably work and would add little overhead was the possibility to specify the Astaro as a DNS proxy for public zones, using a combination of request routing and allowing all clients, not only the ones specified for recursive requests to query those zones.
It also lacks the opportunity to support the AD / Microsoft built in DNS update mechanism that automatically keeps track of DHCP leases as they're handed out dynamically and maps them to the matching DNS name for your AD
Hallo,
thanks for your detailed answer.
So it should work to resolve internal servers and workstations by IP and Name if the informations are set manually.
Could you send a short example how to set up names and domains in the astaro and in a windows system.
Are there differences between Astarto 7 and 8? I played around with this feature some weeks ago but internal resolving didn t work. Astaro 7 and Windows 7.
