IPV6 & DirectAdmin

[yonatanp]

Hello,
I am currently running several servers with DirectAdmin control panel , and with 250 IP addresses per server ( ipv4 ) , I am looking forward to expand my services to IPV6 also, on the Same server machine.

what do I need to do , in order to migrate IPV6 addresses within my current live server?
my provider Does provide me with live IPV6 addresses , and I only need to add them to my NIC to start using them on the server level.

can you please provide me with information about DirectAdmin + IPV6 support?
how do I add my v6 ip addresses to the panel, and how can one client share both ipv4 and ipv6 address for the same domain name?


Would be great to be able to add IPV6 alias for all existing users , so they can have their websites resolve both on v4 and v6, how can that be done? ( can it? )

RIPE space is running out on us, and we need to look forward and provide our end clients with the V6 option as Default on all packages ...

yeah maybe we still got time, but hey - lets get ready!

i would like some help maybe a guide on how to implement my new V6 space in my DirectAdmin panel.

 

[DirectAdmin Support]

Hello,

We are in the process of implementing this.

DirectAdmin does already support IPv6 IP addresses, just not at the same time as IPv4 for the same domain (by default).

Our plans are to add multi-IP support per-user.. and per-domain. This will allow you to have 2 IPs on a domain at the same time.. DA wouldn't care what type.. IPv6 or IPv4 (this would also be handy for IP changes on the same server so the domain never shows the apache or shared IP pages).

This is the early implementation several versions ago:
http://www.directadmin.com/features.php?id=936
but support is better as of 1.34.5.

In any case, at *this* time, if you're looking to have 2 IPs on the same domain, you can do it just fine, it just needs a bit more manual work.

1) Using this guide, copy your 4 virtual_host2*.conf files to the custom directory.
http://help.directadmin.com/item.php?id=2

2) For each value

<VirtualHost |IP|:80>

change it to be:

<VirtualHost |IP|:80 [i]yourIPv6IP[/i]:80>

which would add the IPv6 IP for all virtualhosts on the system.

Note that you can get "fancy" with if-then-else type statements, eg:

|?IPV6TEXT=|
|*if IP="[b]1.2.3.4[/b]"|
|?IPV6TEXT=[b][i]yourIPv6IP1[/i][/b]:80|
|*endif|
|*if IP="[b]1.2.3.5[/b]"|
|?IPV6TEXT=[b][i]yourIPv6IP2[/i][/b]:80|
|*endif|
<VirtualHost |IP|:80 |IPV6TEXT|>

What this does is will only give your IPv4 IPs 1.2.3.4 and 1.2.3.5 IPv6 equivalents... allowing you much much more control.

3) You can then even go farther and even have a checkbox (or field) in your packages with this guide:
http://www.directadmin.com/features.php?id=479

And then using the user_create_post.sh, user_modify_post.sh, domain_create_post.sh and domain_modify_post.sh.. have those scripts check the User's user.conf for your custom item. Then with whatever is set, add code to:
/usr/local/directadmin/data/users/username/domains/domain.com.cust_httpd

which is template code that is inserted into the |CUSTOM| token in the templates. Use if-then-else statements on your cust_httpd code to affect what is inserted into the templates. This allows you to have package items control if you have ipv6 IPs.. and even what IPv6 IP to use if you so wish.


The last step (3) is not required, but is just that extra bit of flexibility if you need it.

Note that.. the other option is to just wait until we finish the multi-IP support for domains. It's the next major feature we'll implement into DA (it might span the next few releases for full completion).


Also, all of your services will need to be recompiled. We will be adding ipv6 support into custombuild at some point as well (likely default to 'off' at first, yet to be determined).

John

 

[yonatanp]

Thank you John,
I will look into these manual tweaks,
Not sure ill do it on a production server yet, but surely will run this on a VPS test machine.

Now I need to find out how to route IPV6 to my VPS machines ( my next vendor to contact .. ) , then the rest is simple httpd.conf work.

In time, We will all have the solution working!