Emacs has a mode for bind files (syntax highlighting, automatic update of version number when saving, ...). This mode is attached to "*.zone" files. As is, if one doesn't know that there is a mode, he won't use the emacs mode. So files "127.0.0" and "localhost" in "/var/bind/pri" should be named "127.0.0.zone" and "localhost.zone"
I have to admit that I like naming the zone files w/ just the name of the domain (or IP address). Not only is it clean, but it also seems to be a bit of a standard. I don't use emacs, though, so I may be biased.
I have to admit that I like the other around and not just because I use emacs :). I like extensions because it gives what the file is immediatly. I agree that often we can get it from the path but it's no garantee (we could have other type of file in the same directory). Especially, I don't like "localhost" has a filename, it's too much like the hostname and that could be confusing in some circumtances. As for the standard isn't "/var/named" a bit more a standard than "/var/bind" for instance (google gives 20400 results for the first and 1280 for the second)? or "/etc/rc.d" vs "/etc/runlevels"? ;)
This is one of those half dozen of one, 6 of the other, I've always had my zone files named as just the domain name since many long moons ago on slackware, so I'm inclined to keep it the way it is on the gentoo ebuilds, of course you and any other user who hapens to use emacs can feel perfectly free to name them blah.foozing or bark.wheezing if you want, but that isn't really something that should become the default under gentoo. This is an opinion, let me see what seemant says about it.
dunno the first thing about bind. Two things: first -- from gentoo's default bind install, how difficult is it for the emacs people to reimplement the zone files? second -- if it really is that difficult, we maybe can do something using the "emacs" USE flag.
One default is as good as an other. Sure nothing keeps me and other to use other names. The idea is that people don't necessarily know that emacs has a mode to handle ".zone" files for Bind. So I could reverse the question: how difficult is it for Slackware users to remove the ".zone" extension? ;) As for using the emacs USE flags. I'm not personnally fond of it. I think it's better if all installation have a standard naming convention by default if the user doesn't want it and say it explicitly (by changing the config files). So to answer the first question, no it's not difficult to change the default (if one knows about the zone extension). For the second thing, I prefer to keep the way it is rather than using the flag. That said, except for habits, what's wrong with renaming the files? I see an advantage to add the extension but I don't see any disadvantage, only a inconvenience for old timers. Gentoo isn't known to be stuck in the past (source distrib instead of binary like most, new way of handling services/runlevels, ...) so this incovenience doesn't strick me as a good reason.
Ok, done in -r1 of bind-9.2.2 please test that as both an upgrade path, and as a fresh install, and let me know on THIS BUG how it goes, thanks.
Well I haven't heard much in the way of complaints so I'm going to close this bug and stabilize the new bind sometime soon...
I'm sorry for this late complaint (updating world now...) One default is as good as an other, but renaming files in *.zone you forced a change for all user with a taste of fews. As any emacs users (me too) know, you can always set an editing mode using special comments at the header or footer of the file. Anyway, please don't change again, keep the .zone extension now. As general rule, changes should be made only if there is a real improvement, no workaround exists and a large number of users asks for it.
