Site move

Just moved this site to a larger VPS. If you can see this message you’re visiting the new host so the migration was clearly a success!

It should also be accessible over IPv6, although this has yet to be tested.

2 thoughts on “Site move

  1. mattie47

    Could be wrong, but I think you need to set up a DNS record for the ipv6 root of your website.

    mattr@mattr-dl:~$ ping al4.co.nz
    PING al4.co.nz (5.79.17.119) 56(84) bytes of data.
    64 bytes from 5.79.17.119: icmp_req=1 ttl=40 time=288 ms
    64 bytes from 5.79.17.119: icmp_req=2 ttl=40 time=281 ms
    ^C
    — al4.co.nz ping statistics —
    3 packets transmitted, 2 received, 33% packet loss, time 2002ms
    rtt min/avg/max/mdev = 281.715/284.916/288.118/3.245 ms
    mattr@mattr-dl:~$ ping blog.al4.co.nz
    PING host2.al4.co.nz (5.79.17.119) 56(84) bytes of data.
    64 bytes from 5.79.17.119: icmp_req=1 ttl=40 time=283 ms
    64 bytes from 5.79.17.119: icmp_req=2 ttl=40 time=281 ms
    ^C
    — host2.al4.co.nz ping statistics —
    3 packets transmitted, 2 received, 33% packet loss, time 2001ms
    rtt min/avg/max/mdev = 281.689/282.709/283.729/1.020 ms
    mattr@mattr-dl:~$ ping6 blog.al4.co.nz
    PING blog.al4.co.nz(2a00:1a48:7804:110:b423:b4f7:ff08:1396) 56 data bytes
    64 bytes from 2a00:1a48:7804:110:b423:b4f7:ff08:1396: icmp_seq=1 ttl=43 time=280 ms
    64 bytes from 2a00:1a48:7804:110:b423:b4f7:ff08:1396: icmp_seq=2 ttl=43 time=277 ms
    64 bytes from 2a00:1a48:7804:110:b423:b4f7:ff08:1396: icmp_seq=3 ttl=43 time=277 ms

    mattr@mattr-dl:~$ ping6 al4.co.nz
    unknown host

    Navigating to http://[2a00:1a48:7804:110:b423:b4f7:ff08:1396]/ returns nothing for me.

    Reply
    1. Alex Post author

      Thanks for the comment, yes you’re correct that this is not working. I don’t think a AAAA record for the domain root is necessarily required for blog to work but it should certainly have one and that was an oversight.

      The real problem is that I haven’t been able to test it properly, as my home network’s ipv6 is currently broken despite working during ipv6 week earlier in the year. Compounding this is my lack of time to sit down and fix it :)

      Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.