bindbackend: "type" omission for zones causes troubles

[terrorobe]

a named.conf entry missing a type field like:

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

will yield:

[bindbackend] Warning! Skipping '' zone 'example.com'

Please also mention the "native" type in the bindbackend docs since it's not clear how the type map to powerdns functionality.

[Habbie]

(note that leaving out 'type' is a misconfig with actual BIND)

[cmouse]

@terrorobe there is no "native" type for BIND either. Leaving type out is misconfiguration as @Habbie pointed out. Perhaps we should fail such config file?

[terrorobe]

@cmouse But in PowerDNS "native" will make sense and give feature parity to other backends.

Failing isn't the most attractive solution, just logging a understandable message might be helpful.

[Habbie]

@cmouse indicated this ticket needs guidance. Here it is: do not error out on this, do something sensible instead, do log something useful. I suspect 'native' is the most sensible default.