Robert Senger robert.sen...@lists.microscopium.de wrote:
Is there a way to identify the source of these reconfig commands?
Turn on process accounting by installing the acct package. Run `dump-acct
/var/log/account/pacct` and look for the rndc entries. The pid and ppid
fields should allow you to
Maybe this, https://wiki.openstack.org/wiki/Designate, is what you are
thinking of.
On Mon, Aug 24, 2015 at 3:29 AM, Ken Peng kp...@runbox.com wrote:
I know it's DNS as a service.
But what's the standard? how to implement it?
Thanks.
___
Please
I have a confusion on how the clients respond to and cache when particularly we
receive negative replies from a DNS Server, particularly NXDOMAIN or SERVFAIL
responses
on the DNS Zone file we have these records
$ORIGIN e164.arpa.
@ IN SOA picardvm2.e164.arpa. e164-contacts.e164.arpa. (
Robert,
While all the advice provided is good, you might also send a suggestion
to bind9-bugs.
The received control channel command message would be more useful if
it included the peer address port e.g.:
... general: info: received control channel command 'reconfig' from
127.0.0.1:48466 .
Am 25.08.2015 um 12:46 schrieb Harshith Mulky:
I have a confusion on how the clients respond to and cache when
particularly we receive negative replies from a DNS Server, particularly
NXDOMAIN or SERVFAIL responses
on the DNS Zone file we have these records
$ORIGIN e164.arpa.
@ IN SOA
5 matches
Mail list logo