Search Again: Re: Preventing zone transfers From: Simon Forster Date: Wednesday, July 11, 2001 Time: 12:43:56 am on 11/7/01 8:12 am, Men & Mice Support at cbuxton@menandmice.com wrote: > Anyway, the basic idea is, assuming you're trying to permit transfers > to an entire class C (or B or A) subnet, you enter the octets covered > by the netmask, followed by ".*". So the 172.16.0.0/16 subnet would > be entered as "172.16.*". 192.168.0.0/24 would be entered as > "192.168.0.*". (Of course, without the quotes.) And > Note that this is different from the way these things are entered on > Mac OS X, Linux, or Solaris servers. In such cases, arbitrary subnets > can be entered as <network number>/<mask length>. Ah. That'll be why that didn't work on MacOS 9.x. Thank you Chris for your pointers. It'll be interesting to see whether the upgrade to 3.5 makes that server more stable. Time will tell. And FWIW, love the complex <NOT> upgrade path. Install 3.5. Copy across data files. Kill 2.2.1. Start 3.5. Enter serial number. Done. Couldn't have been easier. All done via TB2 from the comfort of my office :-) Simon Forster ________________________________________________ LDML Ltd, 4/5 Hazlitt Mews, London, W14 0JZ, UK <tel int="+44 20 7602 9370" uk="020 7602 9370"> <fax int="+44 20 7371 6662" uk="020 7371 6662"> <mailto:simon@ldml.com> ________________________________________________

Messages In This Thread: Preventing zone transfers by Simon Forster on Jul 10, 2001 at 6:01:20 am Re: Preventing zone transfers by Men & Mice Support on Jul 10, 2001 at 6:29:22 am Re: Preventing zone transfers by Simon Forster on Jul 10, 2001 at 6:54:45 am Re: Preventing zone transfers by Men & Mice Support on Jul 10, 2001 at 7:18:29 am Re: Preventing zone transfers by Simon Forster on Jul 10, 2001 at 10:30:53 am Re: Preventing zone transfers by Men & Mice Support on Jul 11, 2001 at 12:13:23 am Re: Preventing zone transfers by Simon Forster on Jul 11, 2001 at 12:43:56 am