Our authoritative servers for the signed TLD ch (NSEC3, no opt-out)
are receiving queries whose qnames are the NSEC3 hashed owner names of
existing delegeations. I suspect that this is a BIND issue (see
below), hence my post to this list.
What I'm seeing is stuff like this:
03-Feb-2010
I just verified this bug on a new install of Centos 5.4
I then downloaded the source bind-9.3.6-P1.tar.gz
And built it with
./configure --with-openssl --prefix=/usr --sysconfdir=/etc
--localstatedir=/var/named
make
Even without actually installing it (just running host from the build area)
I
I'm assuming you downloaded the ISC source rather than RedHat or CentOS.
RedHat back ports bug and security fixes from later BIND versions into
their BIND 9.3.6 implementation (which is why there is extra versioning
in their package names). Since CentOS is built from RedHat source and
both
Thanks adam - Agreed its just host and nslookup, dig is fine.
Duncan
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
On Feb 4 2010, Alexander Gall wrote:
Our authoritative servers for the signed TLD ch (NSEC3, no opt-out)
are receiving queries whose qnames are the NSEC3 hashed owner names of
existing delegeations. I suspect that this is a BIND issue (see
below), hence my post to this list.
What I'm seeing
On 04 Feb 2010 15:39:55 +, Chris Thompson c...@cam.ac.uk said:
On Feb 4 2010, Alexander Gall wrote:
Of the 60 sources in my sample,
26 responded to version queries. All of them identified themselves as
some version of BIND
5 9.5.0-P2
3 9.4.2-P2.1
3 9.4.2-P2
3 9.4.2-P1
3 9.3.4-P1
On Thu, Feb 4, 2010 at 12:12 PM, bsd b...@todoo.biz wrote:
zone abc.com {
type slave;
masters { 213.14.17.2 ; };
file hosts.abc.com;
};
You could put the whole statement on one line, then use grep or sed
based on the zone name.
Operationally, it'd work, and no doubt others
Thanks for your reply…
I know I can do that with grep, but you see I have 270 domains to delete from
my named.conf.
My question was more: has anyone got a working script that I can use in order
to delete name from my named.conf file ?
Idealy It should be a script that I can use in a for
I know I can do that with grep, but you see I have 270 domains to delete
from my named.conf.
My question was more: has anyone got a working script that I can use in
order to delete name from my named.conf file ?
cat named.conf | \
awk 'BEGIN {suppress = 0}
/zone whatever.com/
Thanks Evan,
I'll try that and maybe try to embed that on a bash script…
The formatting should be the same for most of my domains… Anyway I'll test that
on copy of my zone file ;-)
sed and awk haven't got so friendly syntax; but they are indeed very powerful…
Sincerly yours.
Le 4 févr.
On 4 Feb 2010, at 17:12, bsd wrote:
Hello,
I am looking for a script to delete a zone from named.conf and maybe also
from server (zone file).
My zone file looks like that (but could have some variations). Everything
inside brackets should be deleted… and eventually the host file.
On a mail machine I am running a cache-only DNS - BIND 9.6.1-P3.
When I dump the cache I see two lines:
; answer
brainpower-austria.at. 6622MX 5 mx1.bon.at.
I then enter
./rndc flushname brainpower-austria.at
But when I then look at the cache, I still see the MX record
In message 19306.52059.975062.462...@hadron.switch.ch, Alexander Gall writes:
All of those are NSEC3-agnostic. They should not do any DNSSEC
processing for the ch zone, because they don't support algorithm #7.
Yes and no. Just because you are using a algorithm that is unsupported
doesn't
On Thu, Feb 04, 2010 at 06:19:07PM +, Evan Hunt wrote:
I know I can do that with grep, but you see I have 270 domains to delete
from my named.conf.
My question was more: has anyone got a working script that I can use in
order to delete name from my named.conf file ?
cat
I know discussions like this are fun but it took 10 seconds to find the
related change in CHANGES.
2616. [bug] 'host' used the nameservers from resolv.conf even
when a explicit nameserver was specified. [RT #19852]
And it has been applied to these branches.
On Thu, Feb 04, 2010 at 02:27:27PM -0700, Justin T Pryzby wrote:
awk -v s=toxtracker.info 'BEGIN{RS=; s=zone \s\} $0~s{print $0\n}'
Doh, should be:
awk -v s=toxtracker.info 'BEGIN{RS=; s=zone \s\} $0!~s{print $0\n}'
___
bind-users mailing list
In message blu149-w18aec33c220b5f6d2440e585...@phx.gbl, MontyRee writes:
Hello, all.
I have some curious question.
below is a part of zone file at master dns(example.com).
www IN CNAME www.down
down IN NS ns3.example.com.
Hi All,
I found a post on this list from July 2009 with the subject:
Intermittent NXDOMAIN, Bind 9.2.3 config and PowerDNS problem?
https://lists.isc.org/pipermail/bind-users/2009-July/077045.html
I'm having exactly the same issue but with hostname dreamteam.afl.com.au
A sample dig is as
In message 19306.62546.632032.348...@hadron.switch.ch, Alexander Gall writes:
On 04 Feb 2010 15:39:55 +, Chris Thompson c...@cam.ac.uk said:
On Feb 4 2010, Alexander Gall wrote:
Of the 60 sources in my sample,
26 responded to version queries. All of them identified themselves as
In message 260066.10841...@web63105.mail.re1.yahoo.com, Ian B writes:
Hi All,
I found a post on this list from July 2009 with the subject:
Intermittent NXDOMAIN, Bind 9.2.3 config and PowerDNS problem?
https://lists.isc.org/pipermail/bind-users/2009-July/077045.html
I'm having exactly
20 matches
Mail list logo
