Re: bind replication between sites - DNS

This is a discussion on Re: bind replication between sites - DNS ; Dave Henderson wrote: > Gang, > > I have three bind servers running. Two at site 1 (one master and one slave) and the other at site 2. Replication of the zone file seems to take place, but when updates ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Re: bind replication between sites

  1. Re: bind replication between sites

    Dave Henderson wrote:
    > Gang,
    >
    > I have three bind servers running. Two at site 1 (one master and one slave) and the other at site 2. Replication of the zone file seems to take place, but when updates are made on the master server, they don't get replicated to the slaves.

    I don't quite understand that sentence. The file is replicating but the
    changes aren't (???)
    > Here is a snippet from the log of the master if I delete the file on a slave server:
    >
    > Jul 19 13:55:55 localhost named[8329]: client 192.168.0.31#32936: transfer of 'esessen.org/IN': AXFR started
    >
    > and here it is on the slave server:
    >
    > Jul 19 13:55:53 localhost named[7857]: zone esessen.org/IN: transferred serial 3
    > Jul 19 13:55:53 localhost named[7857]: transfer of 'esessen.org/IN' from 192.168.0.11#53: end of transfer
    > Jul 19 13:55:53 localhost named[7857]: zone esessen.org/IN: sending notifies (serial 3)
    >
    >
    > That all seems to work ok, but if I make change to a domain, it doesn't get replicated. There are no records on the master server indicating a transfer at all. The slave contains:
    >
    > Jul 19 13:55:52 localhost named[7857]: zone cliquesoftware.com/IN: sending notifies (serial 2)
    >
    > The actual serial number on the master is 17. Here is the master log (after a restart):
    >
    > Jul 19 11:19:41 localhost named[8329]: zone cliquesoftware.com/IN: loaded serial 17
    > Jul 19 11:19:41 localhost named[8329]: zone cliquesoftware.com/IN: sending notifies (serial 17)
    >

    How long have you waited and what is the REFRESH setting on the zone? If
    there's something wrong with the NOTIFY mechanism for this zone, then it
    could take up to REFRESH time for the changes to replicate.

    If NOTIFY is broken, then that could be tackled as a separate issue.
    Better to establish that normal REFRESH-timed replication works before
    getting into the arcana of NOTIFY.
    > I am getting the following on the master, but I don't have a server or client using the following ip address:
    >
    > Jul 19 12:11:20 localhost named[8329]: client 192.168.0.200#2679: updating zone 'digital-pipe.local/IN': update failed: 'RRset exists (value dependent)' prerequisite not satisfied (NXRRSET)
    > Jul 19 12:11:20 localhost named[8329]: client 192.168.0.200#2682: update 'digital-pipe.local/IN' denied
    >
    >

    Probably just a stupid Wintel client that's misconfigured to register
    its name in DNS.


    - Kevin




  2. Re: bind replication between sites

    Are you changing the serial number when you make a domain update?
    --
    jbeasley@sdf.lonestar.org
    SDF Public Access UNIX System - http://sdf.lonestar.org



+ Reply to Thread