ipv6 adding

webriddler

Verified User
Joined
Nov 5, 2019
Messages
30
I have added an /64 ipv6 and have:

  1. ipv6=1 in my da conf file
  2. assigned to admin user
  3. status is 'shared'
  4. reseller is admin user
  5. linked to ipv4 address
  6. added to Apache
  7. added to DNS
So I believe I have carried out all the steps to get ipv6 working but the ipv6 is not being written to my httpd.conf files which I believe it needs to be?

Any pointers as to what I may be missing? I have done some searching but nothing found
 
Have you tested that you can ping another IPv6 address from the server?

Say can you ping Google IPv6 DNS? ping 2001:4860:4860::8888

Just to verify that it's working.
 
I get
Code:
ping -6 2001:4860:4860:0:0:0:0:8888 connect: Network is unreachable
 
Last edited:
Hi, Yes it's example.tld and the ipv6 is xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx

My DNS is via Hetzner and in my server control panel I have set:


SubnetNext Hop AddressNameservers
xxxx:xxxx:xxxx::/48xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxxNameserver #1: ns1.example.tld
Nameserver #2: ns2.example.tld

I have the above settings but am not sure if the nameservers should point to the DA ones eg ns1.server-xxx-xxx-xxx-xxx.da.direct
 
Last edited:
Yes there are some errors : Did you tried to rewrite conf ? :
Code:
cd /usr/local/directadmin/custombuild
./build rewrite_confs
 
Last edited:
Looks like IPv6 is not set up correctly on your host. Need to make sure that is working first before trying to add it to DirectAdmin. May need to contact your provider to help you get it working, then configure DA.
 
Have gotten a little further and have raised a ticket with my provider to try and troubleshoot this issue:

Code:
ifconfig -a



eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet xxx.xxx.xxxx.xxx netmask 255.255.255.0  broadcast xxx.xxx.xxx.xxx
        inet6 xxxx.xxxx.xxxx.xxxx.xxxx.xxxx  prefixlen 48  scopeid 0x0<global>
        inet6 xxxx.xxxx.xxxx.xxxxx.xxxxx  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xxtxqueuelen 1000  (Ethernet)
        RX packets 204722  bytes 34298099 (32.7 MiB)
        RX errors 0  dropped 5  overruns 0  frame 0
        TX packets 92359  bytes 499483445 (476.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1054  bytes 377753 (368.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1054  bytes 377753 (368.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

So I followed a few guides to enable ipv6 in Centos 7 as this is an unmanaged service but my provider is normally pretty good at sorting stuff like this so fingers crossed. I can ping an ipv6 from my server but cannot yet ping MY server's ipv6 so am close.

DA shows the ipv6 as:

interface is running
valid broadcast is set
resources allocated
supports multicast

Code:
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    inet xxx.xxx.xxx.xxx/24 brd xxx.xxx.xxx.xxx scope global noprefixroute dynamic eth0
       valid_lft 2558152sec preferred_lft 2558152sec
    inet6 xxxx.xxxx.xxxx.xxxx.xxxx.xxxx/48 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 xxxx::xxxx:xxxx:xxx:xxxx/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
 
Last edited:
Have gotten a little further and have raised a ticket with my provider to try and troubleshoot this issue:

Code:
ifconfig -a



eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet xxx.xxx.xxxx.xxx netmask 255.255.255.0  broadcast xxx.xxx.xxx.xxx
        inet6 xxxx.xxxx.xxxx.xxxx.xxxx.xxxx  prefixlen 48  scopeid 0x0<global>
        inet6 xxxx.xxxx.xxxx.xxxxx.xxxxx  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xxtxqueuelen 1000  (Ethernet)
        RX packets 204722  bytes 34298099 (32.7 MiB)
        RX errors 0  dropped 5  overruns 0  frame 0
        TX packets 92359  bytes 499483445 (476.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1054  bytes 377753 (368.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1054  bytes 377753 (368.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

So I followed a few guides to enable ipv6 in Centos 7 as this is an unmanaged service but my provider is normally pretty good at sorting stuff like this so fingers crossed. I can ping an ipv6 from my server but cannot yet ping MY server's ipv6 so am close.

DA shows the ipv6 as:



Code:
ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    inet xxx.xxx.xxx.xxx/24 brd xxx.xxx.xxx.xxx scope global noprefixroute dynamic eth0
       valid_lft 2558152sec preferred_lft 2558152sec
    inet6 xxxx.xxxx.xxxx.xxxx.xxxx.xxxx/48 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 xxxx::xxxx:xxxx:xxx:xxxx/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
Trying to get https://www.example.tld from xxxx:xxxx:xx:xxxx:xxxx:xxxx:xxxx:xxxx... 200 OK :)
 
I always do the opposite : link ipv4 to ipv6
Want to share the domain so that we can check ?
THATS what seemed to do the trick, once ipv6 was configured correctly on the VPS I linked the ipv4 to the ipv6 and it seems to work now, Mythic Beast check gave a 200 response to the webserver query. Thanks for the tip
 
I always do the opposite : link ipv4 to ipv6
Depends on what you want to do, if you want to work with ipv6 then yes probably, I don't know.

If you want to keep working with ipv4 then it's the other way around.
I had to link the ipv6 to the main ipv4 to get the aaa records and get the 1 ipv6 address working.
 
Back
Top