Recent posts

#91

NicTool / Re: Issues installing 2.22

Last post by jwest - May 27, 2014, 04:42:58 PM

the update again assumes your dbserver is localhost, not a huge deal.
upgrade script fails:

applying v 2.16 SQL updates
ALTER TABLE nt_perm ADD column usable_ns VARCHAR(50) AFTER self_write;
DBD::mysql::st execute failed: Duplicate column name 'usable_ns' at /usr/local/lib/perl5/site_perl/5.16/DBIx/Simple.pm line 172, <STDIN> line 1.
at sql/upgrade.pl line 59.

I think I'll just blow it all away and start over with 2.23.

#92

NicTool / Re: Issues installing 2.22

Last post by matt - May 27, 2014, 01:25:13 PM

I think if you update to 2.23 it'll resolve the issue for you. I think this may have been fixed in commit a7bc4f7958641fdf7a716849df6d6e9a7199ade5.

Matt

#93

NicTool / Re: Issues installing 2.22

Last post by jwest - May 27, 2014, 12:27:33 PM

That's awesome matt, makes good sense and I can implement that. Thanks!

Anyone have ideas on what is hopefully the list issue I'm having before going live with nictools? See below....

Through the nictool client I can add/remove nameservers, and add/remove zones. However, I can not add RR's to a zone that was imported, nor can I add RR records to a new zone that I create. The web interface just reports "Failed to complete request". httpd-error.log reports:

DBD::mysql::st execute failed: Incorrect integer value: '' for column 'weight' at row 1 at /usr/local/lib/perl5/site_perl/5.16/DBIx/Simple.pm line 172.
exec_query called by NicToolServer::Zone::Record, 39
        INSERT INTO nt_zone_record(nt_zone_id, name, ttl, description, type_id, address, weight, priority, other) VALUES(??)
        13, test, 86400, , 1, 199.188.211.142, , ,
DBI error: Incorrect integer value: '' for column 'weight' at row 1 at /usr/local/lib/perl5/site_perl/5.16/NicToolServer.pm line 1586.
Client error: 600: : ModPerl::ROOT::ModPerl::Registry::u1_www_nictool_client_htdocs_zone_2ecgi:/u1/www/nictool/client/htdocs/zone.cgi:845 at /u1/www/nictool/client/lib/NicToolClient.pm line 1307.

The above error seems to reference "weight", but I was adding an A record, not an MX record. Previously to the above error I did try to add a MX record, but there wasn't any field to enter the weight :\

Any thoughts to get me running folks? Thanks in advance!

#94

NicTool / Re: IPv6 reverse zone exports,...

Last post by adam.dorsey - May 27, 2014, 09:37:32 AM

Thanks for taking a look.  We found a workaround by using a script to auto-populate the reverse zones based on the forward zones, then the IPv6 deployment got delayed.  When we're ready to move forward with this, I'll upgrade NicTool and see if that fixed the issue.

#95

NicTool / Re: IPv6 reverse zone exports,...

Last post by matt - May 26, 2014, 03:01:04 AM

After reading through the git logs, there were some updates to BIND exports, so it's possible that simply upgrading to NicTool 2.23 (just released) will resolve the problem.

#96

NicTool / Re: IPv6 reverse zone exports,...

Last post by matt - May 26, 2014, 02:37:26 AM

I just finished doing a test of NicTool 2.23, which is slightly different but contains other fixes and changes unrelated to your issue. I set up a BIND export with identical zones and did an export:

Code Select Expand

/usr/local/nictool/ns1 # ./run
nsid 1 reading DB settings from ../server/lib/nictoolserver.conf
nsid 1 has 2 zones, 0 changed, forced, retrieved 2 zones, retrieved 0 zones, exported

/usr/local/nictool/ns1 # cat data-ns1.example.com/1.0.c.1.0.2.1.9.0.2.0.0.0.1.6.2.ip6.arpa
$TTL    86400;
$ORIGIN 1.0.c.1.0.2.1.9.0.2.0.0.0.1.6.2.ip6.arpa.
1.0.c.1.0.2.1.9.0.2.0.0.0.1.6.2.ip6.arpa. IN SOA ns1.example.com.    hostmaster.1.0.c.1.0.2.1.9.0.2.0.0.0.1.6.2.ip6.arpa.. (
2014052604    ; serial
16384   ; refresh
900     ; retry
1048576    ; expiry
2560   ; minimum
)

1.0.c.1.0.2.1.9.0.2.0.0.0.1.6.2.ip6.arpa. 86400 IN NS ns1.example.com.
1.0.c.1.0.2.1.9.0.2.0.0.0.1.6.2.ip6.arpa. 86400 IN NS ns2.example.com.
1.0.c.1.0.2.1.9.0.2.0.0.0.1.6.2.ip6.arpa. 86400 IN NS ns3.example.com.
3.0.0.0.2.5.1.0.0.0.0.0.0.0.0.0 86400 IN  PTR gaea.princeton.rdhpcs.noaa.gov.
4.0.0.0.2.5.1.0.0.0.0.0.0.0.0.0 86400 IN  PTR analysis.princeton.rdhpcs.noaa.gov.
7.0.0.0.2.5.1.0.0.0.0.0.0.0.0.0 86400 IN  PTR mgmt.princeton.rdhpcs.noaa.gov.
8.0.0.0.2.5.1.0.0.0.0.0.0.0.0.0 86400 IN  PTR zeus.princeton.rdhpcs.noaa.gov.

When you run an export, what type of feedback do you get on the command line?  What about in syslog (/var/log/messages on CentOS)?

#97

NicTool / Re: Issues installing 2.22

Last post by matt - May 26, 2014, 02:00:33 AM

A note on the MySQL 5.6 install error, 'Specified key was too long; max key length is 767 bytes'

MySQL is complaining about this column declaration:

Code Select Expand

address             VARCHAR(512) NOT NULL

Address is 512 chars long because of long DKIM signatures and SPF records. But it can also contain utf8 encoded IDN host names, and since utf8 chars can take up to 4 bytes each, a VARCHAR(512) could be up to 2048 bytes long. So MySQL throws an exception. Two things are required to work around this:

1. Use NicTool 2.23 (it sets ROWTYPE=COMPRESSED)
2. Edit your my.cnf and set:

Code Select Expand

[mysqld]
innodb_large_prefix=true
innodb_file_format=barracuda
innodb_file_per_table=true

#98

NicTool / Re: Issues installing 2.22

Last post by jwest - May 23, 2014, 12:15:01 PM

I *think* I've muddled through the export setup process, my zones exported to all nameservers and those servers are responding to the queries with correct answers. I went the route of .../nictool/ns1 etc on the nictool server and just ..../tinydns on the nameservers. That appeared to be right "right way" in any case.

I do appear to have a mildly urgent issue though. Through the nictool client I can add/remove nameservers, and add/remove zones. However, I can not add RR's to a zone that was imported, nor can I add RR records to a new zone that I create. The web interface just reports "Failed to complete request". httpd-error.log reports:

DBD::mysql::st execute failed: Incorrect integer value: '' for column 'weight' at row 1 at /usr/local/lib/perl5/site_perl/5.16/DBIx/Simple.pm line 172.
exec_query called by NicToolServer::Zone::Record, 39
        INSERT INTO nt_zone_record(nt_zone_id, name, ttl, description, type_id, address, weight, priority, other) VALUES(??)
        13, test, 86400, , 1, 199.188.211.142, , ,
DBI error: Incorrect integer value: '' for column 'weight' at row 1 at /usr/local/lib/perl5/site_perl/5.16/NicToolServer.pm line 1586.
Client error: 600: : ModPerl::ROOT::ModPerl::Registry::u1_www_nictool_client_htdocs_zone_2ecgi:/u1/www/nictool/client/htdocs/zone.cgi:845 at /u1/www/nictool/client/lib/NicToolClient.pm line 1307.

The above error seems to reference "weight", but I was adding an A record, not an MX record. Previously to the above error I did try to add a MX record, but there wasn't any field to enter the weight :\

Any thoughts to get me running folks? Thanks in advance!

#99

NicTool / Re: IPv6 reverse zone exports,...

Last post by adam.dorsey - May 23, 2014, 07:27:55 AM

Excellent, thank you.  Please let me know if I can get you any more data.

I'll keep digging on my end and see what I can find out.

#100

NicTool / Re: Issues installing 2.22

Last post by jwest - May 23, 2014, 06:56:44 AM

Hopefully this will be my last question, thanks for the help thus far. I suspect my final issue is due to my lack of understanding of djbdns - I'm new not only to nictool but to tinydns as well (bind convert). I'm having trouble understanding a few things with regards to setting up exports from nictool to tinydns. I suspect most people have issues with the ssh key setup, but that's easy/OldHat to me. I think my confusion revolves around not understanding which host (nictool host vs. nameserver host) certain steps are to be done on.

I followed the excellent notes Matt crafted with regards to setting up djbdns on FreeBSD. Our nameservers are up and running with tinydns just fine. These notes point to using /usr/local/tinydns in your tinydns-conf command. Got that, makes sense, works.

However, the notes for setting up exports point to using /usr/local/tinydns/nsX (where nsX is your nameserver, ex: ns1, ns2, etc.). I am not sure if that is just on the nictools server (so that the data.cbd's for each nameserver are kept in separate folders) or if the ..../ns1 should be done on both the nictools and target nameservers. If the nsX subdirectory is just set up on the nictools server to keep the nameserver directories separate - then when defining nameservers inside nictools are the log and data directories specified as to the local directory structure (ie. /usr/local/tinydns/nsX) or the remote directory structure (ie. /usr/local/tinydns)?

Another point of confusion - the FreeBSD port of nictools automagically creates your tinydns user - and does so with a home directory of /nonexistent. That makes it pretty impossible to "su - tinydns" to do the ssh-keygen. Do I need to change the home directory (and probably shell) for those automatically created uid/gid's? I certainly know how to do that, just hesitating because I'm not sure if nictool is supposed to be set up that way.

Lastly - the "export nictool data to djbdns" document suggests using a "nictool" user for exports. But the run script created appears to hardcode "nt_nictool_export" or somesuch. Do I need to change the export user equate in the run script or is there something in the code that will "figure out" to use nictool user? I saw something in the code that attempts to figure this out - but the run script seems to be hard coded.

Sorry for all the questions, and sincerely appreciate any understanding that can be imparted.

Best,

J