SOA serial number mismatch between Master and Slave Name Ser

[M1LIAM]

I have been trying to set up a VestaCP instance with two Nameserver's. I have followed the documentaion many times over but I am still stuck with one issue ...

The records all update to the second name server but there appears to be a mismatch between the records on the two servers. E.g MyDomain.tld - SOA ****05 on NS1 and MyDomain.tld - SOA *****01 on NS2.

I have spent many hours trying to figure ths out and it doesnt appear to be a known issue in the forum's so any help would be greatly appreciated.

[cagriaksu]

I have the exact same problem, and manually editing the zone file temporarily solves the problem but as soon as I make a change on the master server, SOA serial number reverts on the slave server when it gets updated.

And there is another strange thing, when I run

v-sync-dns-cluster

the SOA serial number on the slave reverts to 01 like it is newly created...

This has to be fixed immediately, so the team please help us.

[cagriaksu]

OK I got to solve it manually, this is how I do it:

Determine which one of the DNS server is left behind. i.e. the SOA serial number is smaller than the other servers.

Login to that server, and run this command for each of the un-sync domains:

v-rebuild-dns-domain dns-cluster xxyyzz.com

Each time you run this command, it ticks the serial number by 1. So if yours is behind 3 numbers, run the command 3 times and check.

I hope that this will be resolved in the next version

[7thkey]

OK I got to solve it manually, this is how I do it:

Determine which one of the DNS server is left behind. i.e. the SOA serial number is smaller than the other servers.

Login to that server, and run this command for each of the un-sync domains:

v-rebuild-dns-domain dns-cluster xxyyzz.com

Each time you run this command, it ticks the serial number by 1. So if yours is behind 3 numbers, run the command 3 times and check.

I hope that this will be resolved in the next version

Hi there, i am having the same issue but I can't run this command to fixit. The thing is that my serial number differs by 7598. Is there another way to acomplish the same task instead hitting 7598 times the "v-rebuild-dns-domain dns-cluster xxyyzz.com" command?

Thanks
Vesta Rules!!

[karlis.kisis]

I have the same problem, so it clearly is a bug.

I like Vesta CP very much so it would be nice to fix it or find a workaround.

I will try the manual fix for each domain as it was suggested some posts ago but that is not a solution.

[krok]

Yeah its a bug, i have it too.

[sim]

Problem still persists...

Imperio, could you please take a look?

For example http://intodns.com/vpsinus.com

Or should we use DNS clusters together with AXFR ?

[drMacFaulty]

Yes, I also experience this issue. Is there already a fix for this?

[drMacFaulty]

Yes, I also experience this issue. Is there already a fix for this?

Tested this now for a few days, but if I add a new domain with slave NS already set up, then sync is as it should be :S
So, for me this issue only arises when I am adding a new name server. The issue persists then and need to be resolved on the new name server.

So, shortly recapped:

- If domain is on master without any slaves and a slave is added, SOA goes out-of-sync.
- If domain is added when master and slaves are already present, sync is as it should be.

[Felix]

I have the same problem.

For serials with a difference of 1 or 2, I use cagriaksu solution. For all other cases I edit the DNS zone manually by editing the following file:

Code: Select all

/home/[USER]/conf/dns/[TLD].db

I too believe this is a serious bug.