Wrong ipv6 in DNS records when creating new virtual server

6 posts / 0 new
Last post
#1 Thu, 01/11/2018 - 23:42

Wrong ipv6 in DNS records when creating new virtual server


I'm currently having a problem with the creation of new virtual servers.

The created DNS gives a wrong IPV6 in AAAA. The good IPV6 is detected and is shown in the new virtual server summary, its also says that its shared by all servers, which is true.

Virtualmin and Webmin network configuration also shows the good IPV6.

The good IP is: 607:5300:60:131d::1

The DNS records contains this ipv6: 607:5300:60:3555::

I tried using "Change IP Adresses" but it does not detect any server with this wrong ip so it doesn't change the dns records...

The only thing i can do is change it manually, which is problematic with all the domains this server host.

I figured this problem when i was trying to fix letsencrypt giving me timeouts, if i manually change the IP everything works fine.

Is there a way to force virtualmin to use the good IP?

Thanks for your help!

Wed, 01/17/2018 - 16:15

Hi again! The problem is still present. No one have an idea why it happens?

Fri, 01/19/2018 - 12:43

First off, 607:5300:60:3555:: this is not a complete address. shouldn’t end in :: Did you get a /64 or /48 from your provider?

If /64 then the first 4 sets of 4 digits dont change. aaaa:bbbb:cccc:dddd:eeee:ffff:gggg:hhhh. E.F.G.H you change. Or aaaa:bbbb:cccc:dddd::HHHH. :: means everything before the HHHH is zeros. like aaaa:bbbb:cccc:eeee:0000:0000:0000:HHHH. Digits can be 0-9 and a-f.

If /48 the the first 3 set of numbers dont change. The 4 set denotes a subnet with /64 ips.

And the 607:5300:60:131d::1 is wrong if you have a /64 as the ::1 is normally reserved for the gateway. Your first available ip would be ::2.

But again, /64/ or /48?

Thu, 01/25/2018 - 15:24

Hi, Thanks for your answer Looks like got a problem with the copy/paste.. Thoses server are from "Kimsufi" (ovh), its low cost and include only 1 ipv4 and 1 ipv6, you can't even get more.

The real ipv6 is: 2607:5300:60:131d::1 The one in the generated dns: 2607:5300:60:3555::

I looked up everywhere on the system and the only place i get the wrong ip is in virtualmin generated dns for my domains.

Fri, 01/26/2018 - 09:02

"I looked up everywhere on the system and the only place i get the wrong ip is in virtualmin generated dns for my domains."

Virtualmin doesn’t generate new IPV6 addresses for new domains unless you've told it to by putting in an ip address range. If you only have 1 ipv4 and 1 ipv6, then there will be no range for either. All domains will get the same shared ip.

In virtualmin, system settings, virtualmin configuration, network settings... you should have your default IPV4 and IPV6 listed there and a button to use them for the default dns records.

Then under virtualmin, addresses and networking, you should only have the 1 ipv4 and 1 ipv6 listed for the default shared ips.

Then under virtualmin, address and networking, change ip addresses... change the IP for all the domains to the correct ips. Then manually check bind dns listings to see if all is correct. If not, change manually.

Sat, 01/27/2018 - 19:20

Hi again!

This is exactly what i did before asking for help here.

As said in my first post, i must change the ip in the bind configuration every time i create a new domain, "change ip addresses" does not work since the virtual server ip is already the good one... Only the bind config have the wrong ip.

I made a script that fix the ip everytime i create a new virtual server so we can say that my problem is fixed.

Topic locked