Going crazy! -- "Sending Notifies" not working on Redhat Enterprise v3??

raiden at wonko.inow.com raiden at wonko.inow.com
Wed Oct 13 16:35:03 UTC 2004


Hello Ronan,

You are absolutely correct that I had the wrong ns in the SOA.  However,
this did not fix the problem.  (I also had another zone, which looks
pretty much exactly like this, except I didn't have the slave ns in the
SOA, and it also is not working.)

Thank you,
-Raiden Johnson


On Wed, 13 Oct 2004, Ronan Flood wrote:

>
> raiden at wonko.inow.com wrote:
>
> Sorry, just noticed something else ...
>
> > ## master -- 64.71.162.42
>
> >         allow-transfer { 64.71.162.46; };
>
> > ## zone file on master
> > $TTL 3h
> > myvemma.com. IN SOA ns1.myvemma.com. support.myvemma.com. (
>
> > myvemma.com.    IN NS   ns1.myvemma.com.
> > myvemma.com.    IN NS   ns2.myvemma.com.
>
> > web01.myvemma.com.              IN A    64.71.162.46
> > web02.myvemma.com.              IN A    64.71.162.42
>
> > ns1.myvemma.com.                IN CNAME        web01.myvemma.com.
> > ns2.myvemma.com.                IN CNAME        web02.myvemma.com.
>
> When deciding which servers to notify, the master will ignore the
> server mentioned in the SOA as the primary server.  In your case,
> that would be ns1 which (indirectly) has address 64.71.162.46, which
> appears to be your slave!  Have you got the addresses for ns1/ns2
> the wrong way around?
>
> --
>                       Ronan Flood <R.Flood at noc.ulcc.ac.uk>
>                         working for but not speaking for
>              Network Services, University of London Computer Centre
>      (which means: don't bother ULCC if I've said something you don't like)
>


More information about the bind-users mailing list