- Newest
- Most votes
- Most comments
@Riku_Kobayashi I have wodpress bitnami running on Dual stack, now when i create snapshot and try to move to IP6 only option, its not allowring. It seems even AWS lightsail is not supporting bitnami wordpress with IP6
Hello.
As you know, if your ISP does not support IPv6, you will not be able to access it even if Lightsail migrates to IPv6.
It is possible to create a Lightsail instance with both IPv4 and IPv6 in a dual-stack configuration, but in the end you will incur IPv4 costs because you have an IPv4 address.
https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-ipv6-reachability.html
If you want to completely migrate the Lightsail side to IPv6, I think you should create a Lightsail instance with a blueprint that allows IPv6-only settings and install WordPress.
https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-ipv6-only-plans.html
Well the whole idea is to avoid the cost and make sure people can see the site. IPV6 is out of question, maybe few years down the track. IPV4 costs money. What did you do? keep using IPV4?
If users accessing your website only have access to public IPv4, you must continue to use public IPv4 with Lightsail. If you can eliminate users who can only use public IPv4, move to IPv6.
Thanks for getting back to me quickly. Well it is a public WordPress site, so eliminating anyone from it is not ideal. I use IP address as "A" record and point to the site. Just briefly, I use MS365 for most of my emails and so I point the domain using MS nameservers and host my DNS records there and from there again, using "A" record point to my AWS WordPress Lightsail Instance. Is there any other way to do this, but not pointing the NS to AWS?
I think you should register Lightsail's IPv4 address as an A record in the MS DNS zone you already have.
Well this is how it currently works, I have the IP of the instance added as "A" record pointing to the AWS WP Site. What I am asking is is there a way to utilize IPV6 only instance and assign a domain under AWS Lightsail and somehow pointing to domain to that instance. I am not really sure what I going on about, just looking for a solution I guess.
Hi,
You are able to associate a domain name to a IPv6 address via AAAA record. But as you correctly noted, users of your website need to have IPv6 support in their internet setup to be able to view your website. That requires ISP, modem, and even network routers between user and your server to support IPv6. Until a general adoption of IPv6 support, you are better off using a dual stack instance (with support for both public IPv4 and IPv6 address) to host your content for public use.
Also note that Wordpress blueprint and plugins don’t support IPv6 addresses yet. They require a public IPv4 address.
Hope that answers your question. And Thank you for using Lightsail.
Relevant content
- asked 23 days ago
- asked 3 months ago
AWS OFFICIALUpdated 4 months ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 13 days ago
Yes, I did this as well and you are right, I was also not able to move to IPV6 only instance. I am not sure why AWS are forcing users to do this for WP as from what I understand, WP is not compatible with IPV6, so is the majority of the World by standards, this is just to charge extra, I sense YES as I do not see a real solution to their option .