False positive on inscure zone update by IP?

Hi, today I noticed the following log messages from my caching-only bind on startup: zone 'localhost' allows updates by IP address, which is insecure zone 'version.bind' allows updates by IP address, which is insecure zone 'hostname.bind' allows updates by IP address, which is insecure zone

RE: Enterprise DNS Architecture - AD and BIND

Same here. Slave the AD zones, all end-user machines use BIND-based (Infoblox) servers for resolution, on Anycast addresses. DHCP servers (also Infoblox) update DNS for the clients, with the client names being registered in non-AD zones (some of which are defined by geography, with a generic

Re: Enterprise DNS Architecture - AD and BIND

On Tue, 8 Nov 2016 16:09:36 -0800 Ray Van Dolson wrote: Greetings; Am reviewing our DNS setup which has organically evolved over the years and most certainly is due for an update: - We have AD servers responsible for our primary domain (internally). - We have other

Re: DNS and cache-expiration modification

I think prefetch (enabled by default) already does what you need although in a different way. https://deepthought.isc.org/article/AA-01122/0/Early-refresh-of-cache-records-cache-prefetch-in-BIND-9.10.html Daniel On 18.11.16 10:24, Job wrote: > Hello, > > for heavy-use cache improvements, i

Re: DNS and cache-expiration modification

On 18 Nov 2016, at 9:24, Job wrote: Do you know if with Bind is possible? Perhaps the configuration option 'max-cache-ttl' is what you're looking for ? Best regards, Niall O'Reilly ___ Please visit

DNS and cache-expiration modification

Hello, for heavy-use cache improvements, i was thinking to "alter" the expire time of cache records. I would like to try to "alter" the expiration of records present in cache. Do you know if with Bind is possible? Thank you, /F ___ Please visit