Issue IPv6 ranges not working as they should

[samip537]

Hi,

When I add an IPv6 range like 2a01:4f9:2b:f810:0:0:0:1 -> 2a01:4f9:2b:f810:ffff:ffff:ffff:ffff (Mask /64), it will only use the 2a01:4f9:2b:f810::1 address for all of the sites, and not allocate one IP per site from it, why's that? I don't think that's how it's supposed to work?

 

[ChristophRo]

You did not add an IPv6 range to the server, but the single IPv6 address 2a01:4f9:2b:f810:0:0:0:1
And the same way an IPv4 subnet mask of 255.255.255.0 does not mean you added 256 IP addresses to your server, a /64 subnet mask for IPv6 does not do that.

 

[samip537]

You did not add an IPv6 range to the server, but the single IPv6 address 2a01:4f9:2b:f810:0:0:0:1
And the same way an IPv4 subnet mask of 255.255.255.0 does not mean you added 256 IP addresses to your server, a /64 subnet mask for IPv6 does not do that.

Then how are you supposed to do that for IPv6? In almost all other instances, outside Plesk that's understood as a prefix as I cannot simply do 2a01:4f9:2b:f810::/64 as it will not accept it, but most other applications does accept it.

 

[ChristophRo]

You cannot configure IPv6 ranges on a server, that is not something that is supposed to work.
And Plesk really works and behaves the same way with IPv6 as every other software does.

You cannot add the IPv6 Adresse 2a01:4f9:2b:f810:: with Subnet Mask /64 to your server, as this is the "network" address. (the same way you cannot use like 192.168.1.0 on a /24 IPv4 Subnet)
You can use 2a01:4f9:2b:f810::1 with Subnet Mask /64 on your server though (if that is not the gateways address) and of course you can enter many more IPv6 addresses from that range, if you want to use a dedicated address for every web on your server.

 

[samip537]

You cannot configure IPv6 ranges on a server, that is not something that is supposed to work.
And Plesk really works and behaves the same way with IPv6 as every other software does.

You cannot add the IPv6 Adresse 2a01:4f9:2b:f810:: with Subnet Mask /64 to your server, as this is the "network" address. (the same way you cannot use like 192.168.1.0 on a /24 IPv4 Subnet)
You can use 2a01:4f9:2b:f810::1 with Subnet Mask /64 on your server though (if that is not the gateways address) and of course you can enter many more IPv6 addresses from that range, if you want to use a dedicated address for every web on your server.

For example, if you give a Docker daemon v6-fixed-cidr of 2a01:4f9:2b:f810::/64, it will in fact allocate ::1 to itself and all others in order to containers so it's understood as a network prefix, so why's this any different?

You are supposed to be able to configure a IPv6 prefix of /64 for hosting sites on.

 

[ChristophRo]

Yeah, the Docker daemon acts as a network device (i.e. Router) and the containers get/learn their IPv6 address via IPv6 autoconfiguration from this daemon.
Just similar like you would configure a DHCP service on the Docker daemon (or Router) for IPv4 and the clients/container then get their IPv4 address from that.

 

[trump9666]

Truly it is not allowed to configure DNS settings on the remote DNS server, you can only view the information about the registered domain name. "DNS settings" link (located at the site with a domain name ) will be replaced with the "Whois information".