Bind Cluster Slave Servers and serials on cluster server that are higher

Submitted by signet on Tue, 07/15/2014 - 09:56 Pro Licensee

Hi,

One of our customers has two Virtualmin servers, one as a primary DNS server and one as a second, which is added at the "Cluster Slave Servers" panel. This is working ok, when he creates a domain the domain is also added at the second DNS server.

The problem is that when the customer changes something in DNS, the zone on the primary DNS server gets a serial which is lower than the original serial. This causes the problem that the secondary nameserver doesn't see the updates.

See the logfile entries below: Jul 15 15:28:33 son-levix3-dc1 named[30427]: zone overslagbedrijfvankessel.nl/IN: serial number (1403081696) received from master 78.108.137.47#53 < ours (1405330889) Jul 15 15:29:54 son-levix3-dc1 named[30427]: zone hollandshitsfestijn.nl/IN: serial number (1403081697) received from master 78.108.137.47#53 < ours (1405338664) Jul 15 15:31:19 son-levix3-dc1 named[30427]: zone oostenburgereiland.com/IN: serial number (1403081697) received from master 78.108.137.47#53 < ours (1405331559) Jul 15 15:35:50 son-levix3-dc1 named[30427]: zone penningspvc.nl/IN: serial number (1403081696) received from master 78.108.137.47#53 < ours (1405160189) Jul 15 15:36:12 son-levix3-dc1 named[30427]: zone shinko-benelux.com/IN: serial number (1403081697) received from master 78.108.137.47#53 < ours (1405079574) Jul 15 15:38:05 son-levix3-dc1 named[30427]: zone lijmbedrijfbrover.nl/IN: serial number (1403081696) received from master 78.108.137.47#53 < ours (1405339984) Jul 15 15:41:20 son-levix3-dc1 named[30427]: zone multi-com.nl/IN: serial number (1403081696) received from master 78.108.137.47#53 < ours (1405338346) Jul 15 15:43:26 son-levix3-dc1 named[30427]: zone sernechannelmarketing.com/IN: serial number (1403081697) received from master 78.108.137.47#53 < ours (1405081955) Jul 15 15:43:54 son-levix3-dc1 named[30427]: zone oostenburgereiland.nl/IN: serial number (1403081696) received from master 78.108.137.47#53 < ours (1405331466) Jul 15 15:45:04 son-levix3-dc1 named[30427]: zone lithercourant.nl/IN: serial number (1403081696) received from master 78.108.137.47#53 < ours (1405339860) Jul 15 16:08:19 son-levix3-dc1 named[22546]: zone rommecontainerservice.nl/IN: serial number (1403081699) received from master 78.108.137.47#53 < ours (1405087399) Jul 15 16:10:18 son-levix3-dc1 named[22546]: zone rommecontainerservice.nl/IN: serial number (1403081699) received from master 78.108.137.47#53 < ours (1405087399) Jul 15 16:11:48 son-levix3-dc1 named[22546]: zone wihabo.nl/IN: serial number (1403081714) received from master 78.108.137.47#53 < ours (1405424372) Jul 15 16:11:50 son-levix3-dc1 named[22546]: zone supersinglesparty.nl/IN: serial number (1403081697) received from master 78.108.137.47#53 < ours (1405068797) Jul 15 16:13:34 son-levix3-dc1 named[22546]: zone po2belettering.nl/IN: serial number (1403081698) received from master 78.108.137.47#53 < ours (1405089723)

How can this happen, en more important, how can we solve this issue?

Is it possible to change the serial on the primary server to something more useful such as the date for example.

Thanks!

Justin.

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Wed, 07/16/2014 - 02:51

That's odd - Virtualmin should always increment the serial on the master by 1 for each change.

Are the serials on the slave perhaps being changed by something outside of Virtualmin? Or if you manually fix the serial on the slave to be the same as the master, do they stay in sync for subsequent changes?

Submitted by signet on Wed, 07/16/2014 - 03:28 Pro Licensee

Thanks for your reply, I've created a script which retransfered each affected domain, so the problems are solved for now. I will keep an eye on this to see if it returns.

Submitted by signet on Mon, 07/28/2014 - 04:05 Pro Licensee

Hi,

This ticket can be closed, it was a script from the end-customer who caused this problem.

Sorry for the inconvenience caused!

Thanks,

Justin.