Accessing nameservers above #10

monachus · December 12, 2006, 08:34:42 AM

i've looked around for an answer to this, and before i start mucking with the source, i thought i'd post the question here -

i have 8 nameservers at the top level of my nictool tree. some of my clients, in sub-groups below the top level, have their own nameservers. when i create a zone in one of the subgroups, i can only see 10 nameservers in the list, starting with the ones at the top level. if the client has more than 2 nameservers, those nameservers are not available to me for selection at the time of zone creation.

what i've been doing is creating the zone and then using my addserver script to remove the invalid nameservers and add the other ones. i'm wondering if it's possible to view _all_ nameservers for the top-level through to the current sub-group, or to cycle through them?

matt · December 14, 2006, 06:51:05 PM

That's simple. Don't delegate all your top level nameservers to the subgroup. After creating the subgroup, edit it and remove all the nameservers from your top level that the subgroup shouldn't be able to see anyway.

monachus · November 19, 2009, 08:24:39 AM

Quote from: matt on December 14, 2006, 06:51:05 PM
That's simple. Don't delegate all your top level nameservers to the subgroup. After creating the subgroup, edit it and remove all the nameservers from your top level that the subgroup shouldn't be able to see anyway.

Hi, Matt. Sorry to bring this up again, but we're still having a problem with this. In 2006 I implemented a workaround that no longer works by reorganizing the sub-groups. I'm not able to do that anymore, and we still have an issue with only 10 nameservers appearing in the list. I've looked under the sub-group, and while I see that I can remove permissions that allow them to delegate to those servers, the servers still appear in the list. Is it because I'm a user at the top-level that they still appear?

arces.net (sub-group) <- I'm a user here. There are 8 nameservers defined.
-- client.arces.net (sub-group)<-- I enter client internal zones here because they share our nameservers with theirs. Let's say that they have 4 internal servers.
-- -- zone.client.arces.net (zone)<-- I still see all nameservers except the last 2 of the client's.

matt · November 13, 2011, 12:34:53 PM

Hi Adrian,

See this file: https://github.com/msimerson/NicTool/blob/master/server/Changes

Pay special attention to the 2.10 updates. Especially the one that starts like this:

SQL: Fixed the data model for zone nameservers. Replaced the abhorrent nt_zone.ns0..nt_zone.ns9 columns with the table nt_zone_nameservers.
* there's no limit on how many nameservers a zone can publish to

monachus · November 14, 2011, 10:11:05 AM

Quote from: matt on November 13, 2011, 12:34:53 PM
SQL: Fixed the data model for zone nameservers. Replaced the abhorrent nt_zone.ns0..nt_zone.ns9 columns with the table nt_zone_nameservers.
* there's no limit on how many nameservers a zone can publish to

HOT! I'll get that in the queue for deployment. Thanks for restructuring it!

monachus · November 21, 2011, 08:23:40 AM

Matt - the download page lists 2.08 as the latest version. Is 2.10 available from SVN or elsewhere?

matt · November 21, 2011, 09:39:30 AM

There's a dowload link in the NicTool Developer's corner with a direct link to the 2.10 tarballs and the Changes file on GitHub.