Hi
I was considering to use the syslog on a different host for logging from
bind. The purpose was to collect logs from various places into one
repository.
This is not a busy installation so performance is not expected to be a
problem.
I looked in the arm but could not see where I could put the
Why u are using mapped{} options in dns64 conf ???
What we are doing is:
dns64 2001:db8:5200::/96 {
Clients {
2001:db8:1000:10::/64;
2001:db8:20:10::/64;
...
};
};
From: bind-users-bounces+gaurav.kansal=nic...@lists.isc.org
Sten
The syslog daemon on the machine where BIND runs on will send the syslog
messages to the central syslog server. So you need to configure your
syslog.conf file to send the facility that BIND uses, normaly daemon, to
the remote syslog server.
The syslog.conf on Solaris looks something
It's syslogd's job to relay messages to other servers. You
need to configure syslogd to do this for named.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
On 30/05/2012 11:16, Sten Carlsen wrote:
Hi
I was considering to use the syslog on a different host for logging
from bind. The purpose was to collect logs from various places into
one repository.
This is not a busy installation so performance is not expected to be a
problem.
I looked in
We have a lab setup where we are testing a customer configuration but do not
have all of the same equipment.
Is it possible to have a bind server that resolves certain FQDNs in a zone,
while forwarding the remaining to another DNS?
We tried putting forwarding in the zone, that did not work,
I think the normal way to do this is run a syslog server on the host
running bind, which is configured to just forward all log messages to
the remote syslog server. Otherwise, bind would have to implement the
syslog network protocol(s) itself, rather than just use the system
standard local syslog
On 30.05.12 12:16, Sten Carlsen wrote:
I was considering to use the syslog on a different host for logging from
bind. The purpose was to collect logs from various places into one
repository.
[...]
Can bind send its logging output to an external syslog?
Not directly. However, that is what
On 30.05.12 04:03, Stephen James wrote:
We have a lab setup where we are testing a customer configuration but do not
have all of the same equipment.
Is it possible to have a bind server that resolves certain FQDNs in a zone,
while forwarding the remaining to another DNS?
not with BIND. Bind
On 30/05/12 12:03, Stephen James wrote:
We have a lab setup where we are testing a customer configuration but do
not have all of the same equipment.
Is it possible to have a bind server that resolves certain FQDNs in a
zone, while forwarding the remaining to another DNS?
Not easily. You could
I am trying to validate DNSSEC signature of top level zone using dig.
I do the following:
dig +nocomments +nostats +nocmd +noquestion -t dnskey . trusted-key.key
dig +topdown +sigchase +trusted-key=./trusted-key.key +multiline com
and get the result like this:
[-many line
OK, I've built myself a bind 9.8.3 setup so I can use the 'external'
update-policy. It seems there are a few details not fully described in
the 9.8.3 ARM :) I did have a bit of a look at the list archives but I
couldn't find anything which immediately answered my questions...
* If the external
On Wed, May 30, 2012 at 06:35:56PM +0400, Nikolay Shaplov wrote:
I am trying to validate DNSSEC signature of top level zone using dig.
dig +sigchase is known to have serious flaws (that's why it's not
compiled in to BIND 9 by default). Our long-term plan has been to rewrite
it completely. So
Hi
Thanks for good answers, I now know what to do and how to proceed.
Thanks.
On 30/05/12 13:17, Matus UHLAR - fantomas wrote:
On 30.05.12 12:16, Sten Carlsen wrote:
I was considering to use the syslog on a different host for logging from
bind. The purpose was to collect logs from various
14 matches
Mail list logo
