[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Restricting who can secondary off your primary named
- Subject: Re: [cobalt-users] Restricting who can secondary off your primary named
- From: Gerald Waugh <gwaugh@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon Apr 8 22:55:47 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Mon, 08 Apr 2002, Roy A. Urick wrote:
> what about those of us who really dont care, and didnt put ANYTHING in the
> box, and are getting log alerts that legit servers are being refused
> updates???
>
> according to the book if you dont put anything in, ANYONE can do transfers.
> is it different for raq4's and the book is wrong?
>
> PS I would put in the IP of the server, but alas this particular server is
> on a dynamic IP via ISDN (it provides secondary, and is "primary" for
> internal PC's for private IP DNS within the NAT-ed network)
>
if the slave is on a dynamic IP, How does the master know where to send
the NOTIFY?
I know cobalt calls them primary and secondary, but the up2date terms are
Master and Slave. But then we can't call the coblts up2date either.;-)
--
Gerald Waugh
http://www.frontstreetnetworks.com
Front Street Networks LLC - 203-785-0699
229 Front Street, Ste. #C, New Haven CT, 06513-3203