On 1/3/2011 4:15 AM, Lars Müller wrote:
On Fri, Dec 31, 2010 at 04:52:53PM -0800, Marc Chamberlin wrote: [ 8< ]
1. Do NOT use the Yast DNS server tool to do any configuration for you, if you wish to use Views. It is braindead about both views and include mechanisms and will simply trash your work on you, I don't think it can handle em yet. Which bug report have you filed? ID please.
Lars - I will be happy to file a bug report, but protocol dictates that I first discuss an issue here on the newsgroup before doing so. So am waiting to hear what everyone thinks first, and if the consensus is to file it as a bug report, then I will do so...
2. The organization of files for the named server is somewhat difficult to comprehend. It is not really clear what files get copied out of the /etc directory over to the chroot directory /var/lib/named and what don't without grokking the scripts. Sorry, here I'm not able to follow you. /etc/sysconfig/named clearly states what's done. If the documentation isn't clear or straight enough file a bug report.
Discussiong an issue on a list isn't a bug report. ;)
It certainly is not clear to me, but then I didn't write the scripts and code so grokking is a bit tougher... One thing I have finally figured out is that specifying .conf files to be included for a view, in /etc MUST use an absolute path specification. A relative path name in an include statement will force the user to execute the rcnamed script from within the /etc directory. This of course means that these files will end up under /var/lib/named/etc/... I can live with that but it wasn't exactly what I was expecting or hoping for...
What is worse is that all the config and include files exist in a flat space in /etc. This could use some reorganization so that all named files exist under a single root directory, IMHO, so as to make it easier to comprehend what files go where. Then you have to rename and reorganize the structure of the named %files section. And this results in changing the location of files. This includes the risk to break running configurations.
Unfortunately moving configuration files which are tagged as %config(noreplace) in the %files section of the spec file isn't that easy. Hmmm now I don't follow you, think you are talking about something else.. What %files section? What do you mean by tagged as %config(noreplace)? I have not seen anything in the Bind/Named documents talking about this!
In particular the built in include mechanism does not assume anything about exactly where to find include files, and if one uses it as I did, to create separate directories to hold the config files for each view, then it will force you to run the rcnamed script from the /etc directory. Either the implemantation is broken or you've not read the comments in /etc/sysconfig/named
Please consider to open a bug report for this particular include issue. Well as I said, I tried to read, but didn't grok... see above comments...
The fact that the rcnamed script will prepend the chroot dir path to the source file/dir name when creating the target dir, for these copy operations, forces one to use relative paths names, which is why rcnamed can only then be used from within the /etc directory once include files are defined. This is either a poor design of this script or a file model is being used that is not well documented or intuitive to understand, again IMHO! And this sounds like you've not read the comments in the sysconfig file. Either use relative path names or fully qualified file/ path names.
3. Last, be careful of using rcnamed when restarting the server. It can and will delete files and directories in the /var/lib/named area without doing any kind of backup first. That is poor programming on someone's part also and breaks a fundamental rule of good computer science - NEVER delete or change user data without backing it up first and making sure you have a good backed up copy before making such changes, or deleting it!!!... This is covered by which bug ID? No report in bugzilla = no issue.
Which files are deleted or overwritten?
Lars Initially, I had tried to set up relative path includes for the .conf files that describe each of my views. So for example, I set up files such as /etc/internal/internal_zones.conf and /etc/external/external_zones.conf. My include statements read like: include "internal/internal_zones.conf" where I was hoping it would end up at /var/lib/named/internal/internal_zones.conf. As I mentioned above I have subsequently determined that this forces one to execute rcnamed from within the /etc directory otherwise the includes will fail.
But that said, I then wanted to place all of my zone domain configuration files within the internal or external directories so as to keep them associated with the aforementioned .conf files. So for example, my internal_zones.conf file could have a zone specified like - zone "marcchamberlin.com" in { file "internal/marcchamberlin.com"; type master; ... }; and it was these zone domain configuration files that got deleted on me... (the file "internal/marcchamberlin.com" contains all the actual DNS record specifications) I don't know how to set things up so that these zone domain configuration files could get copied from /etc though I tried to fool around with it a bit... Anywise, for now I have separated the .conf files so they are in the /var/lib/named/etc directory and my zone domain configuration files are in /var/lib/named/internal and /var/lib/named/external. I can edit those directly now and not worry about them being clobbered.. Am willing to file a bug report, as I mentioned, if that is the group consensus. I also admit that I do not fully grok the architecture and file structure intention yet, for this server, so I may be missing something and wanted to discuss it first... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org