This is a discussion on Re: unknown option 'allow-update' within the Bind Users forums, part of the DNS and Related Forums category; > I currently have a primary name server and a secondary name server. > The plan is to add a ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
> I currently have a primary name server and a secondary name server. > The plan is to add a third shortly. Every zone on the primary needs to > be pushed to the slaves when a zone is updated. This works, but it's > not secure. > > Before I look at TSIG for doing this "properly" I'd like to get > ip-restricted updates working. > When using allow-update in the options part of the config, This is maybe not what you want: The "allow-update"-statement is used to allow your secondary (or any other server) to send a DDNS-update to you. Not for receiving one from you. For this you need a NS-entry for your new secondary in the zone. > I get the > following error: > named[2108]: /etc/bind/named.conf.options:45: unknown option > 'allow-update=' Where comes the = from? The statement should be allow-update { 1.2.3.4; } There is no = bye, Tom. -- +++ Neu: Echte DSL-Flatrates von GMX - Surfen ohne Limits +++ Always online ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl |