cant find the zone files that im adding ,where are tehy being populated in my server

[chamambom]

i have the following config

Hostname Method Config File Server Root Zones Directory Actions
myserver.com cron /etc/named.conf /var/named/chroot/etc/named.conf /var/named/chroot/var/named /var/named/chroot/var/named

im in a chrooted environment

and my issue is ,where are the zonefiles that im adding ......cant sem to find them in my server on the configured zone directory

[chamambom]

and when i try to build my config via ssh ,its saying config build failed but when i use cron ,it just says This server will be updated on the next cron run. ...and how frequent does it run

[WillyXJ]

Zone files are stored in your configured zones directory, so in your case they would get stored in /var/named/chroot/var/named. They will get populated once you have a successful config build.

During your client installation (php /usr/local/facileManager/fmDNS/dns.php install), you get prompted for the update method. Based on your selection, the installer will make the necessary changes to your client to proper communication. If you selected 'cron' at that time, it would add the necessary five minute cron entry for root's crontab (you can view this with crontab -u root), if you select 'http' then it will configure httpd, and if you select 'ssh' then it will add the ssh key.

This makes me realize there's a usability issue in that you could select 'http' during the install, but then change the update method via the webui to cron or ssh and the necessary changes won't be applied to the client.

If that's the case for you and you want to update via cron, then you can run through the install process again and select the update method you plan to use or manually add the following on your client:

sudo crontab -e
*/5 * * * * /usr/bin/php /usr/local/facileManager/fmDNS/dns.php cron

I'll leave this issue open to track a fix for the usability.

[chamambom]

i figured it out a little bit later that cron might be failing because it wanted me to re-run the client ...will give it a try today at night again....and do you have any idea on whether in a chroot environment it works with no issues ,will give it another try when im less sleepy and get it running ....

and can you confirm , does it automatically pick up the zones in the zone directory or i have to do something and another confusing thing ,the options parameter in named.conf does it work with file includes and is it also the one that will be containing all the references to the zone records line this

zone "trunkcall.co.zw" {
type master;
file "/var/named/trunkcall.co.zw";
allow-query {
any;
};
};

[WillyXJ]

Good questions. fmDNS writes the zone files to the zones directory that you specify and it also uses that value in your zone definitions for the "file" directive. I have not tested it in a chroot environment, but it should work just fine. I'm interested to hear your test results in that situation.

[WillyXJ]

In your case, it looks like you'll want to define your zones directory as /var/named as named will take care of the chroot prefix.

[chamambom]

Hello willy

thanks for the update on that issue , but i have a few questions concerning the configurations
i have the named.conf file with the following excerpt

acl trusted {

196.44.191.0/24;

    100.0.0.0/24;

};

include "/etc/named.conf.zones";
zone "158.221.41.in-addr.arpa" {
type master;
file "/var/named/41.221.158.rev";
};
zone "149.221.41.in-addr.arpa" {

through fmDNS ,am i able to use the include parameter as im not seeing it in the options config file

[WillyXJ]

You currently cannot define your own "include" statements. fmDNS will automatically generate the zone files, zone definition files, and proper include statements in named.conf (or named.conf.local on a Debian-based system).

[chamambom]

thanx for your prompt feed back ,really need to get it working soon as possible ... will definitely contribute a lot more once im done .....and another issue currently bugging me ...

on the update methods i have chosen cron ...what does it mean when it says This server will be updated on the next cron run and after 5 to 10 mins ,my named.conf still hasant been updated ...

[WillyXJ]

That's sounds like the cron entry didn't get created on client install. See my previous comment at #54 (comment)

Let me know if that did not resolve the issue.

[chamambom]

i guess im making progress ,the cron entry was not referencing my relative path of the dns.php config file and as soon as i changed it to */5 * * * * /usr/bin/php /usr/local/facileManager/fmDNS/dns.php cron ,i could see my named had changed accordingly...will keep you updated on whatever i find ...