Hello,
On Nov 8, 2012, at 22:48 , a b wrote:
> > Using purely DNS for zone replication (supermaster) is nice and sounds
> > great, but also has disadvantages, e.g. it is not reliable: If the
> > NOTIFY could not be delivered to the slave, then the slave is
> > inconsistent. So, you need anothe
> Using purely DNS for zone replication (supermaster) is nice and sounds
> great, but also has disadvantages, e.g. it is not reliable: If the
> NOTIFY could not be delivered to the slave, then the slave is
> inconsistent. So, you need another mechanism to verify and update slaves
> which failed
Hi Peter,
Success! I removed the old in-addr.arpa and added a more specific
3.2.1.in-addr.arpa zone and both reverse queries now resolve!
Thanks, Gordon
Peter van Dijk-6 wrote:
>
> Hello Gordon,
>
> On Nov 6, 2012, at 14:50 , GordonJB wrote:
>
>> I have a PDNS server set up with a zone and
Hello Gordon,
On Nov 6, 2012, at 14:50 , GordonJB wrote:
> I have a PDNS server set up with a zone and reverse zone for our domain
> (here 1.2.3.4), and have the recursor configured to forward requests not in
> our recognized zones to another DNS server on the network (here 1.2.0.4).
> While this