LOT OF PROBLEMS with zone import in ISPCONFIG

Discussion in 'General' started by HanSol, Mar 17, 2014.

  1. HanSol

    HanSol New Member


    I had more than 10 years experience to create/modify zone files in Linux.
    I just simply edited the .conf file in /etc/bind or /etc/bind9/ directory then reload/restart the bind service and all perfect. If needed to add new records, just added to .conf file and reload service.

    We moved to ISPCONFIG 3, to all will be more simply and nice.
    What I see now it's a NIGHTMARE about zone import and ISPCONFIG 3.
    Please show me the way what I do wrong.
    What I now see it's not possible to be a real ISPCONFIG 3 functionality.

    Please help if you can.

    I want import and update a full zone file, but "Zone File Import" function working badly for me. I first time use ISP Config. In manual I not found and solution for that.

    First of all, I tried a lot of options before post this question.

    I know: if I want to import abc123.com domain, the best if I name as: abc123.com.txt . It's ok.


    PROBLEM 1.: If I set NS records at zone file, like:

    abc123.com. 86400 NS ns11.nsexample.com.
    abc123.com. 86400 NS ns12.nsexample.com.

    will be replaced to this after text import:

    abc123.com. 0 NS server.hostname.com.

    Where "server.hostname.com" is the server name.
    This is so annoying and this import function is useless.
    What I do wrong?
    What need to set to zone text file to don't happening this?

    I tried to import file from /etc/bind/pri.abc123.com file, what is the proper server version, what I edited manually. Also fail to importing the ns records: replace NS records to this line:

    abc123.com. 0 NS server.hostname.com.

    Summary: ISP Config cannot import his own proper config file back with " Import Zone File" function from /etc/bind/ .

    (Just for fun: ISPCONFIG is Microsoft product, this is why not compatible with itself? :rolleyes: How possible to cannot import his own /etc/bind/ file back from upload?! :confused: What I do wrong? It's not possible! )

    PROBLEM 2.: How can I set the NS record name at DNS Zone menu / NS named record from imported zone file?

    I not found any way to set the primary NS record name when importing zone file, just if I set it manually.
    It also need to import it from text zone file. If I need to import 1000 zones, then I set it manually all NS and all custom settings? I hope it's just a joke and I don't know something or I use zone import badly. Impossible to this zone import do this as I expected.

    PROBLEM 3.: How to import "Allow zone transfers to these IPs (comma separated list)" line?

    No way to set also manually 1000 times this setting.
    What need to set to text file to get this settings from text file?

    PROBLEM 4.: How to import "Client" line?

    Also, it's impossible to set manually all times the client if I import, 1000 times.

    (Maybe not I am who want to use this zone import function first time ever in ISP Config. Btw... this is version 3 and not working as needed. What do the 1 or 2 version? I don't want to know it, if this is the ISP Config 3 functionality...)

    PROBLEM 5.: How to update the zone file from text file?

    Maybe again I do wrong: If I try to import again the abc123.com.txt, it's NOT UPDATE THE ZONE! Not detect the new line in text file and not insert the new A record to zone. Why?
    I am the first ISP Config client who want to use zone update this function ever?

    Real file example, how can I update now the zone file from text:

    I want update abc123.com zone file from text file, because added 500 new A record:

    1. I delete abc123.com record from dns (maybe this time not working the zone, so bad way, but no other way to import text again)

    2. I upload the modified abc123.com.txt file.

    3. I manually (IT'S A JOKE!!!) edit the NS line at "DNS Zone" tab

    4. I manually (IT'S A JOKE!!!) edit the owner line at "DNS Zone" tab

    5. I manually (IT'S A JOKE!!!) edit "Allow zone transfers to these IPs (comma separated list)" line at "DNS Zone" tab

    6. Save...

    7. I manually (IT'S A JOKE!!!) switch to "Records" tab and I edit the

    abc123.com. 0 NS server.hostname.com.

    line to:

    abc123.com. 86400 NS ns11.nsexample.com.

    8. I manually (IT'S A JOKE!!!) switch to Records and I add a new line:

    abc123.com. 86400 NS ns12.nsexample.com.

    9. I save the zone.

    So, if I want to change the zone in text file, every times need to do this 9 steps, manually? :confused: Please tell me, I'm a newbie and I do wrong and this 9 steps not needed to do in ISP Config 3 to update a zone from text file.

    Please just tell me what I do wrong.

    ISP Config cannot work as I described up here, maybe I do really wrong something.

    I'm calm and finding the solution to use ISPConfig.

    I heard ISP Config is professional tool and developed from 2005.
    What I use, the ISPCONFIG truly 9 years old product? Or it's just a beta application with a lack of general features?
    I'm so confused about this.
    It's cannot be a 9 years old product or I so newbie.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You are using a really old version of ispconfig on your server. The current ISPConfig version is and you have installed.

    Your whole problem arises out of the fact that you modify zone files on the shell manually instead of creating / modifying the zones in ispconfig with or using the remote api for mass modification of zones.

    Also nobody is importing 1000 zones manually, if you import larger amounts of config data from another controlpanel or from any kind of files, then you do that with a script that connects to the ispconfig remote api. See example and documentation in the remote_client folder of the ispconfig tar.gz file. The zine import function you refer to is for importing a single zone, not for mass imports. Another option is to do the modfcations in the dns_rr table in mysql and then use the ispconfig resync tool to write out the changes to bind, but the remote api is safer and the recommended way.
    Last edited: Mar 17, 2014

Share This Page