3 nameservers possible ?

[squirrelhost]

anyone know of a workaround to
allow 3 nameservers ?

i.e. this would mean being able to
enter 3 nameservers in the admin settings,

or being able (on rare occasions) to
set up reseller, with 3 nameservers,

and, of course any welcome mail
including such a setup for a new user
or reseller, listing the 3 nameservers
to use.

( I'm not discussing clustering etc,
just being able have DA use 3
namservers where required, rather
than 2 as it appears currently)

 

[Watje6]

As far as I know, it's not yet possible. We also use 3 nameservers and I have to manualy add our ns3 in the zone file.

 

[squirrelhost]

I noticed ns1 and ns2 are hardcoded into
DA binary, so no flexibility there.

I've resisted manual editing as I currently
maintain a dozen non-DA servers with
customers who insist on a minimum of
3 diverse nameservers, and I did look
forward to no editing on the DA ones..

ho-hum...

 

[nobaloney]

You may be able to do something...

If you've got only one ns3 servername for the entire server or if each domain has it's own ns3 servername:

Move the /usr/local/directadmin/data/templates/named.db file to /usr/local/directadmin/data/templates/custom/.

Edit it in the custom directory:

After this line:

|NS|

create another line.

For the first example above (one ns3 servername for the entire server):

|DOMAIN|.      14400      IN      NS      ns3.example.com.

where example.com should be replaced by the domain name of your 3rd nameserver (don't forget the "." wherever I've shown it; it's important).

For the second example above (each domain has it's own ns3 nameserver:

|DOMAIN|.      14400      IN      NS      ns3.|DOMAIN|.

Then to update all the zone files:

# echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue

(The "#" mark means run it as root.)

To actually create the slave zones:

I don't know if the new DA slave zone functionality will do it; I do know that my master2slave DNS replicator will.

Please watch for typos in the above code; I do NOT run it on my servers.

Jeff

 

[squirrelhost]

Jeff,

i did consider adding one custom line
as you did, but it really wouldn't work
on a server with different users/resellers
having diverse requirements.

In my ideal world, it would be possible
to have:

1. default 'global' template directory

2. one 'custom' template dir, as is currently
available

and
3. a per-reseller (or -per-user?) custom
template directory.

then any actions would look for a template
directory in the order 3), 2), 1).

but it's only a dream at tme moment.

Note that this would of course apply
to any conf file.

 

[Kyra]

have u ever found a solution for this question?

With Regards,

Marco