Hello people,
I'll try to answer your questions...
So what does this actually mean/do:
> Give support to mix static direct resolution with dynamic one
> Give support to mix static reverse resolution with dynamic one
> Give support for dynamic DNS reverse resolution under /var/lib/bind/ directory
and
> Added support to add DNS reverse resolution for DHCP clients
specifically with respect to the feature requests that were outlined in this thread?
Are static DHCP leases now reflected in DNS lookups? Even if they are not actually issued (that is, the hosts use a static IP assignment)?
Both dynamic and static leases are reflected in DNS lookups if you configure the dynamic DNS. The new features are basically to accept the hostname sent by the DHCP client for dynamic leases. Static leases still uses what Zentyal says to use. From now on, the member name is used to set the hostname in the dynamic DNS. Furthermore, this release allows you to query the reverse resolution as well for DHCP clients. Finally, these dynamic DNS zones may have static records as well.
To give you an example to depict this features:
Dynamic DNS zone: local.lan
DHCP range: 10.0.0.10-10.0.0.20
DHCP fixed address: object A
Object A: Member b - 10.0.0.2
Dynamic host introduces itself as "portable"
The DNS records will be:
b.local.lan <-> 10.0.0.2
portable.local.lan <-> 10.0.0.11
Did you see the benefits?
Are the contents of the /etc/hosts file used in DNS lookups now?
No, it doesn't. As Zentyal does not manage
/etc/hosts, neither the DNS module does in any way.
Bad points:
1/ dhcp crashes because /etc/bind/keys has not secret
key "my.domain." {
algorithm HMAC-MD5;
secret "";
};
maybe a timeout while generating keys?
I think you have spotted a bug. The key generation is only done in creation. The zones which are not created with the new packages and it is not a dynamic zone, then the key is not generated. I will fix this issue right now and we will publish a new package.
Sorry for any inconvenience and thanks very much for your feedback!