Now that RFCs 7434 7435 have been published, how do ISC see the future
of the seemingly ever-expanding built-in empty zone list in BIND?
One possibility that seems plausible to me is to add EMPTY.AS112.ARPA
to the list now, and remove existing entries if and when the corresponding
names in the
Am 14.05.2015 um 18:29 schrieb Chris Thompson:
Now that RFCs 7434 7435 have been published, how do ISC see the future
of the seemingly ever-expanding built-in empty zone list in BIND?
One possibility that seems plausible to me is to add EMPTY.AS112.ARPA
to the list now, and remove existing
On May 14 2015, I wrote:
Now that RFCs 7434 7435 have been published, how do ISC see the future ...
That should be 7_5_34 7_5_35 of course. Curses.
--
Chris Thompson
Email: c...@cam.ac.uk
___
Please visit
On 14/05/15 22:02, Bischof, Ralph F. (MSFC-IS40)[NICS] wrote:
Hi Ralf,
symptoms I am seeing is that a dig command sends out several queries
with EDNS and bufsize of 4096. The server on the other side of this
I think this is the pertinent point. You're testing with dig, but dig
doesn't
Hello,
I am trying to understand EDNS queries and the fallback capabilities.
BIND 9.9.6-P1. I have a particular scenario where two sites are connected via
firewall links and UDP fragmentation is not allowed. The symptoms I am seeing
is that a dig command sends out several queries with
On Thu, 14 May 2015, Chris Thompson wrote:
Now that RFCs 7[5]34 7[5]35 have been published, how do ISC see the future
of the seemingly ever-expanding built-in empty zone list in BIND?
One possibility that seems plausible to me is to add EMPTY.AS112.ARPA
to the list now, and remove existing
Add before we get the ticket to add it.
4117. [protocol] Add EMPTY.AS112.ARPA as per RFC 7534.
Mark
In message alpine.lfd.2.11.1505141429250.6...@daffy.loonybin.net, Rob Foehl
writes:
On Thu, 14 May 2015, Chris Thompson wrote:
Now that RFCs 7[5]34 7[5]35 have been published, how
Another option might be changing 'file' to 'syslog' then using stuff like
:msg, contains, 'skipping nameserver' stop (or whatever pattern you want
to match) in your rsyslog configuration.
http://www.rsyslog.com/doc/rsyslog_conf_filter.html
-Original Message-
From: Reindl Harald
Am 15.05.2015 um 02:01 schrieb Nick Edwards:
skipping nameserver 'ns5.concord.org' because it is a CNAME, while
resolving '210.128-25.119.138.63.in-addr.arpa/PTR'
I have logs grow by about 30 megs a day with pretty much only this in
it (of course not always same remote server), how do I
You can silence the messages by sending category cname to null, but
have you tried contact the zone administrator postmas...@concord.org
to get the delegation fixed. One of the points of logging the
configuration error is to make it visible so it can be fixed. The
second reason is to have
skipping nameserver 'ns5.concord.org' because it is a CNAME, while
resolving '210.128-25.119.138.63.in-addr.arpa/PTR'
I have logs grow by about 30 megs a day with pretty much only this in
it (of course not always same remote server), how do I shut this up ?
My logging statments are
logging {
11 matches
Mail list logo
