19:36 -0800, Steve Koon wrote:
[ ... ]
> Anyone know why I am getting this "not authoritative" message and no
> zone file on .118 all of a sudden?
[ ... ]
> This is the log message in the 69.25.129.118 slave
>
> client 69.25.129.117#1304: received notify for zone
I am getting on one of my slaves (69.25.129.117) yet on the other I get
the zone to come across from the master. Just a quirk here is that the
.117 slave has to be recycled before the zone comes across yet the .118
comes across when the master is recycle and a change has occurred in one
of the zone
I have one of my zones that is not showing one of the A records when
using Dig anyone know why this is happening?
emailclickA 64.186.224.244
Thanks,
Steve
=== Zone file content on secondary
$ORIGIN .
$TTL 900 ;
We have moved a zone from UltraDNS to our DNS server 1 week ago and it
is still not showing us as authority. Can anyone help me as to why this
might be happening and how to fix it? I have included a dig below using
a public dns server (4.2.2.1) and our dns server (69.25.129.117) where
is shows no a
4 matches
Mail list logo