Add to Favourites Add to Favourites    Print this Article Print this Article

IPv6 - How To

As of DirectAdmin 1.37.0, there have been several improvements to better support IPv6.
This guide will outline where we're at with support and how to use DirectAdmin with IPv6.

  1. The first step, is to tell DirectAdmin that you want to use IPv6.  To do this, set ipv6=1 in /usr/local/directadmin/conf/directadmin.conf by running:

    /usr/local/directadmin/directadmin set ipv6 1
    service directadmin restart

  2. Adding IPs to DirectAdmin is done the same way as with IPv4 IPs:

    Admin Level -> IP Manager

    Note that the netmask only applies for IPv4 IPs and will be ignored here.
    The IPv6 mask format, eg: /64 is not yet supported.  When adding IPs you can use either the full or short form, but DA will expand it to the full format of IPv6 values.  Don't use [] around the IP here, just the IP is fine, eg:  1:2::9
  3. You can assign IPs to Users normally, as with IPv4.  As of 1.37.0, the multi-IP system allows you to assign both an IPv4 and IPv6 IP to an account.  See this guide on how to do that.
    NOTE: If you're upgrading to 1.37.0+, and want to use the mutli-IP system, you must convert to the unified ftp password format.  Systems installed with 1.37.0 won't need to.   You'll know you need to convert if you can't find the tables for "Additional IPs".
  4. The DNS system should be ready for IPv6.  We have the dns_a.conf and dns_aaaa.conf default records for newly created zones.  Each of these template files have checks on the IP type.  When an IP is sent to the template, the IP type is also included, so the template can chose to ignore adding any records if the IP type doesn't match it's format, or (with customization) you can add some other value if you'd like.  For most people, leaving it along will be best.
    NOTE:  Backup/Restores with the multi-ip system and dns are yet complete.   If you use multiple IPs on a domain, you may need to adjust the zone after restore as the "Additional IPs" may still be in the zone, even if the account is on a different IP.


In order to connect to to a service with IPv6, that service must be compiled to support IPv6.

DirectAdmin: For 1.37.0 and older, DirectAdmin can setup configs with IPv6, but doesn't support IPv6 for connections on port 2222.
However, for 1.37.1, DirectAdmin can now allow incoming connections on IPv6 on 2222.

Apache: Apache support IPv6 out of the box. No need for changes.

Exim: Exim does support IPv6, but you need to ensure it's compiled in.  To check, type:

[root@server ~]# /usr/sbin/exim -bV | grep Support
Support for: crypteq IPv6 Perl OpenSSL move_frozen_messages Content_Scanning DKIM Old_Demime

which should give you an output similar to above.  Ensure you see IPv6 in the output.
If you don't see IPv6 in the output, then you'll need to recompile exim, either using rpms, or from source.  The latest Makefiles should have the required HAVE_IPV6=YES to ensure it's included.

Dovecot: Dovecot supports IPv6 out of the box. No need for changes.

ProFTPd: ProFTPd support IPv6 out of the box. No need for changes.

Bind: (named) You might need to add this code to the options section of your named.conf:

listen-on-v6 port 53 { any; };

Was this answer helpful?

Also Read