NicTool
problem running zone2nic.pl
Hi, when I run zone2nic.pl, I get (nictool ) 0 # ./zone2nic.pl -z one.zone -s our.nameserver -a Name "NicToolServerAPI::use_https_authentication" used only once: possible typo at ./zone2nic.pl line 62. Logged in as test test Importing one.zone: Cannot encode unnamed element as 'hash'. Will be encoded as 'map' instead 300 - Sanity error: The mailaddr format replaces the @ with a . (dot). *** Failed to create one.zone: Sanity error : The mailaddr format replaces the @ with a . (dot).
But I don't know where the problem is. The zone doesn't contain any "@" in the SOA record or in any other record.
I've commented out the check and now I can at least import stuff via zone2nic.pl. Our zones should be OK in that respect.
This is with PERL 5.18 (on my "dev" install locally in Fusion), but I get the same error at work on my slightly older PERL 5.16 install (all FreeBSD 10).
Hey @rduffner, have you checked out zone2nic since #86 was merged? Would you mind?
I'll check it out tomorrow. Could you package 2.32 in the meantime? Or is it not ready, yet?
So, for the sake of completeness, this is what I get from an axfr from our current nameserver (anonymized to protect the guilty): drill axfr @dns.bla.dom thezone.dom thezone.dom. 3600 IN SOA ns.bla.dom. postmaster.bla.dom. 2014120303 10800 3600 604800 3600 thezone.dom. 3600 IN MX 10 mx01.thezone.dom. thezone.dom. 3600 IN A 12.34.56.78 thezone.dom. 3600 IN NS ns.bla.dom. thezone.dom. 3600 IN NS ns2.bla.dom. mx01.thezone.dom. 3600 IN A 12.34.56.78 test.thezone.dom. 3600 IN A 12.34.56.78 www.thezone.dom. 3600 IN A 12.34.56.78 www2.thezone.dom. 3600 IN A 12.34.56.78 thezone.dom. 3600 IN SOA ns.bla.dom. postmaster.bla.dom. 2014120303 10800 3600 604800 3600
And this is what zone2nic says to it:
00 - Sanity error: The mailaddr format replaces the @ with a . (dot). *** Failed to create thezone.dom: Sanity error : The mailaddr format replaces the @ with a . (dot).
I can import the zones, if I hardcode the SOA to the postmaster address (which I'm thinking of doing anyway). Still, I'd like to know what the problem is with the SOA we have there now.
I thought I had fixed that, I must not have committed that change yet. Basically, a module that we depend on got more strict, and the import script is reporting that error. I just rewrite the first dot with an @, and then pass that value in.