Recent changes to bugs

IP Report incorrect for non-class C zone.

2006-06-16T13:02:03Z

The IP report appears to assume that the reverse zone
is always a class C we have an entire class B in a
single zone, the report shows the first two and the
last octet of each host rather than the first two and
last two octets.

Problems importing bind9 standard configuration

2005-04-20T11:51:49Z

It seems that the import utility does not work wilth
bind9 config files.

I have setup a Fedora 3 Core system with bind,
bind-utils and caching-nameserver rpms.

Trying to import from directory of probind/etc:

./import -v -a -d
/var/www/html/probind/named/test/named.conf
Checking database for readyness.
OK
Found 1 servers in the database with NS records.
Opening /var/www/html/probind/named/test/named.conf ...
Found zone: 'localdomain'

...

Script simply does not come to an end, looping ...?

Regards Frank

Frank.Elsner@rz.uni-osnabrueck.de

Yet Probind2 is just what we need, but I urgently need
to import existing zone files.

Probind and fedora 2 issues

2004-11-18T21:45:12Z

It appears there is a problem with the default install of
bind and probind on Fedora Core 2.

Fedora core 2 install chroot bind. This is for security,
however probind does not know of the chrooted dir.

The problem it causes:

It creates db.zone files in /var/named.

However the chroot runs
in /var/named/chroot/var/named.

It can create the files fine, but when named starts it
starts chrooted thinking
that /var/named/chroot/var/named is the
actual /var/named and the db. files do not exists in that
directory.

Youc an update the path where the zones live in
probind, but that creates another problem. When it
writes the named.conf file it writes:

options {
directory "/var/named/chroot/var/named";
};

which when named runs in chroot mode, the dbfiles may
exists now in /var/named/chroot/var/named

but now bind is looking for the db files
in /var/named/chroot/var/named/chroot which doesnt
exisists because bind thinks you are in /var/named
(because of chroot) and there is no /var/named/chroot
in the chrooted directory. if that makes sense?

import script problem

2004-06-25T07:26:44Z

Whilst trying to use the import script to import
existing data the script hangs after finding the first
zone.

Workaround

The format of the zone files was ex.

zone "test.com" in {

the import script doesn't understand the 'in' before
the open brace. After editing the zone files to the
below format the import work successfully.

zone "test.com" {

Secondary named.conf bug

2004-03-10T12:14:26Z

mknamed.conf doesn't take options when constructing the
secondary named.conf:

Line 38
return "zone \"$domain\" {\n\ttype slave;\n\tmasters
{\n\t\t$masters;\n\t};\n\tfile \"SEC/$zonefile\";\ n};\n\n";

My line:
return "zone \"$domain\" {\n\ttype
slave;\n\tmasters {\n\t\t$masters;\n\t};\n\tfile
\"SEC/$zonefile\";\n
".($options? "\t$options\n" : "") ."};\n\n";
}

Testing SOA/NS fails where DiG is happy (top-level domain)

2003-10-29T11:36:44Z

Using frame generated by test.php (Testing),
with "Host/IP" left empty, a request for a SOA or NS
record for a top-level domain for which I have set
ProBind2 up for (fake root using "master" instead
of "hints" + appropriate delegation on same BIND9
server) fails.

("request: domain {type=SOA} server: ares.domain
{10.3.3.3} results: Test Failed")

DiG on *same* host returns correct values as expected.
(dig domain soa)

tcpdump reveals:
ProBind2 asking for "domain.domain.", where
DiG asks for "domain."

second level domains (subdomain.domain) work fine on
both and ask for the right value.

All domains created without any trailing dot in name, but
correctly generated with dot in zone file.