knotc compile/reload - knot-dns-users

1 Bře 2012

Hello,

Congratulations to the release of Knot 1.0 which I'm looking at a bit
now, starting off with a minimal configuration.

	system {
	  storage "/etc/knot";
	  user: "root";
	}

	interfaces {
	        ipv4 { address 127.0.0.1@53; }
	}

	keys {
	        my-key hmac-md5 "xxxx";
	}

	remotes {
	        local0 { address 127.0.0.1; }
	        mastr { address 192.168.1.145; }
	        m2 { address 192.168.1.53; key my-key; }
	}

	zones {
	        example.com {  
	                file "example.com.zone"; 
	        }

	        inline.aa {
	                file "inline.aa";
	                semantic-checks off;
	                xfr-in mastr;
	                notify-in mastr;
	        }

	        jpmens.net {
	                file "jpmens.net";
	                semantic-checks off;
	                xfr-in m2;
	                notify-in m2;
	                xfr-out local0;
	        }
	}

Apologies for nitpicking on these rather cosmetic issues, but maybe they
can be addressed in a future version:

An invocation of `knotc -c knot.conf compile' complains that slave zone
files don't (yet) exist. (True enough: they haven't yet been
transferred):

        Zone file 'inline.aa' doesn't exist.
        Zone file 'jpmens.net' doesn't exist.
        Parsing file 'example.com.zone', origin 'example.com.' ...
        Compilation successful.

After launching Knot with `knotc -c knot.conf start', zones are
populated from the master server(s) and I see the *.db and *.db.crc
files. The zones are loaded and I can query them. So far, so good. :)

A small change to `example.com.zone' and a compile, again warns that the
slave zone files don't exist. In effect it is true: the filenames I've
configured in knot.conf do not exist, but the message is confusing
because the zones have been loaded/exist.

        knotc -c knot.conf compile
        Zone file 'inline.aa' doesn't exist.
        Zone file 'jpmens.net' doesn't exist.
        Parsing file 'example.com.zone', origin 'example.com.' ...
        Compilation successful.'

A subsequent server reload `knotc -c knot.conf reload' says in the log
that the file(s) I just compiled are out of date:

        Loading 3 compiled zones...
        warning: Database for zone 'example.com' is not up-to-date. Please
recompile.
        Loaded zone 'example.com.'
        Zone 'inline.aa.' is up-to-date, no need for reload.
        Zone 'jpmens.net.' is up-to-date, no need for reload.
        Loaded 3 out of 3 zones.
        Configuration reloaded.

Regards,

        -JP