Currently we have (for our Master zone) a list of IPs that can update
our DNS master using the allow-update statement:
zone "redacted.ac.nz" {
type master;
allow-update {
::1;
127.0.0.1;
131.123.103.2;
131.123.88.3;
...
}
We are wanting to transition to the more modern update
Hi Andrew,
On 9/04/2011 12:37 a.m., andrew wales wrote:
>
> Remember that rndc dumpdb doesn't actually dump the cache to stdout.
> Has it actually written to named_dump.db in named's working directory?
> Regards,
>
> Andrew
Thanks - you are spot on here :-) I was expecting the DB to be writte
On 8/04/2011 10:11 p.m., Tony Finch wrote:
> No, only DNS requests that are handled by the server itself are cached.
> There is no sniffing going on.
>
> Tony.
Thank you for the clarification. If I add "nameserver 127.0.0.1" to the
VM (and comment out the existing name servers) and attempt to r
I am new to using BIND and thought that I would start by setting up a
caching-only name server on a VM running CentOS 5.5. While in this
mode, my understanding is that named should be passively listening for
any DNS requests that are resolved and be adding them to its local DB.
Adding localhost t
4 matches
Mail list logo
