Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.glorb.com!usenet.stanford.edu!not-for-mail From: Jan-Piet Mens Newsgroups: comp.protocols.dns.bind Subject: Re: Securing zone transfer and DDNS Date: Thu, 10 Nov 2011 17:38:56 +0100 Lines: 11 Sender: Jan-Piet Mens Approved: bind-users@lists.isc.org Message-ID: References: <21ed7915.4729b742.4eb72f52.7f82@o2.pl> <32DD7227-7F82-4D63-A4BF-D038031CCB1A@isc.org> <85ecc83.4a6e4d68.4eb81652.18c6d@o2.pl> <20111107230426.1A07F16D8A25@drugs.dv.isc.org> <4b476ffb.2625d518.4ebbf979.d1c4b@o2.pl> NNTP-Posting-Host: lists.isc.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1320943155 14427 149.20.64.75 (10 Nov 2011 16:39:15 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bind-users@isc.org To: Aleksander Kurczyk Return-Path: X-Original-To: bind-users@lists.isc.org Delivered-To: bind-users@lists.isc.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent:sender; bh=OkWKuXTC3fqnMnJJuZEDImR9BIZ7T7g+bMXytaj2qVQ=; b=t94Mzxi08iWEGG9na/f964tsDtCAodbYkY77CZiKEjG5Za2520/n3ngV16Hz/gvYm8 URNHK6+UnA/L6KJ/mbFVwAqMuIs95AIii4nxx2lJe7qVNXvhJnYAfBON5DtmBiAimW/R dJuTWoIdiT/1Ksfnxva9HfctmEKak9YVaeuv4= Content-Disposition: inline In-Reply-To: <4b476ffb.2625d518.4ebbf979.d1c4b@o2.pl> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mx.ams1.isc.org X-BeenThere: bind-users@lists.isc.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: BIND Users Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: x330-a1.tempe.blueboxinc.net comp.protocols.dns.bind:89 > I have one more question - how can I block every update for every zone > in options section using update-policy? Are you actually *reading* the documentation: the ARM actually defines `allow-update': "Specifies which hosts are allowed to submit Dynamic DNS updates for master zones. The default is to deny updates from all hosts." -JP