I have an orphaned dns site entry that I can only get to via search and all child entries (A, CNAME, MX, etc) have their relationships broken and can't be accessed at all. After searching for the parent entry and deleting that and waiting about 30 minutes for the recycle bin to actually be available I thought I removed the entry. Recreating the entry is still resulting in ISPConfig claiming the SOA exists already.... Any ideas? I am perpetually running into this orphaning issue and have actually completely refreshed the OS install on the box a couple times to insure a fresh system before installing ISPConfig.
Do you men the entries are left in the databse or on the harddisk? The DNS-Manager has a recycle bin for every reseller and one for the admin, are the records in one of these recycle bin's and have you emptied all recycle bins? Do you get any errors in the ISPConfig logfile /home/admispconfig/ispconfig/ispconfig.log ?
I ended up fixing this by finding the entry via search and then putting it in a new parent folder. Not that it matters, it looks like the DNS setup is so hosed it wont actually update the zonefiles for any of the domains that are being configured via ISPConfig. No errors in the ISPConfig log. Is there anyway I can force ISPConfig to actually write the entries to the zonefiles?
actually, come to think of it, I'm not entirely sure how or why, but I keep getting blank folders in my "DNS Manager" tree. There is no New Folder icon for that manager... Something is really messed up again, perhaps I have to reinstall again?
Not sure if anyone is still looking at this thread but.... After some digging, it looks like ISPConfig is pointed to an invalid location for it's zonefiles dir. It wants to goto /etc/named whichdoes not exist. The zonefiles are located in /var/named/chroot/var/named. Installation was performed according to the Centos 4.4 howto on howtoforge. I'm thinking this item may be why it is unable to update the zonefiles when I make changes to records from within ISPConfig. I attempted to make a change to this and the change did not take, after checking back into ispconfig later the setting was changed BACK ot /etc/named. I think my nextstep will be to do a symlink.
One of the steps in the Perfect setup is to create a symbolic link between /etc/named to your ch-root-ed directory
It can be tough for a blind man to read braile on an LCD. I must have skipped that line Even with the symlink ISPConfig is still not updating the zonefiles. In fact, ISPConfig has not updated the zonefiles in 4 days. Any other ideas what could be going on here?
Looks like I had the same problem as alot of people, even with the permissions set to the dirs properly as well as that symlink linking /etc/bind to the chroot jail still failed ot get my updates to post. I did the following things: updated the server_bind_zonefile_dir value in the mysql db to /var/named/chroot/var/named removed the lockfile added a dns entry to a domain in ISPConfig deleted that entry after doing those things, the zone file was updated. I'm wondering, how long do those lockfiles sit around, are they supposed to go away ever?
