named.conf file being overwritten

Discussion in 'Installation/Configuration' started by jonwatson, Nov 7, 2008.

  1. jonwatson

    jonwatson New Member

    Hi All,

    We are attempting to change some nameservers in the origanization and are running into problems. The ISPConfig instance is currently a slave to another master nameserver. We need to make the ISPConfig instance the master. To that end, we've created all the necessary records and have changed the slave record in the /var/named/chroot/etc/named.conf file from:


    zone "server.net" {
    type slave;
    file "sec.server.net";
    masters { xx.xx.xx.xx; };
    };

    to

    zone "server.net" {
    type master;
    file "pri.server.net";
    };

    (I munged the IP address, but it is valid)

    However, once a day, the 'slave' entry is re-added to the named.conf file and causes BIND to fail to start because there are now two server.net entries.

    I've searched the server and the DNS manager in the GUI and I can't find this slave entry anywhere. I assume that it is stored in a template or something somewhere otherwise ISPConfig would not know about it and not keep re-entering it into the named.conf file.

    Does anyone know where I should look to stop this from happening?

    Thanks,

    Jon
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Empty all recycle bin's in the dns manager.
     
  3. jonwatson

    jonwatson New Member

    Hi Till,

    That didn't help, unfortunately. I emptied the recycle bin, but whenever I make any change to any DNS record, ISPConfig is writing those changes as well as the erroneous slave record back into named.conf still.

    Any other ideas where to look? Any customized templates or config files somewhere that I need to look at?

    Thanks,

    Jon
     
  4. falko

    falko Super Moderator ISPConfig Developer

    Not sure what happened, but you can create a backup of the ISPConfig database and then delete the records from the database (you must also delete them from dns_dep and dns_nodes). If you mess up your database, you can restore it from the backup.
     
  5. jonwatson

    jonwatson New Member

    Hi,

    I'm not sure what you mean. Emptying the database will just take down my ISPConfig system. Maybe you're saying I should only empty certain tables or something? Not sure.

    In any case, I have been through almost every table in the database and I don't see anything that looks like this slave record. I've also grepped inside every text file in the /var/named dir for the slave record hoping to find a customized conf file or something that it is coming from, but no luck.

    This slave record must be stored somewhere or ISPConfig wouldn't know how to write it. Where could it be?

    Jon
     
  6. falko

    falko Super Moderator ISPConfig Developer

    Sorry if my post was confusing, but I meant that you should delete only the records of the slave record from the database.
     

Share This Page