Hi
No, there's no duplicated directives in the zone file. For example,
here's the zone for another domain with the same error and here are the
only directives:
$ORIGIN x.com.
$TTL 3600
Tom
At 20-07-2012 09:56 PM +0100, Tony Finch wrote:
On 20 Jul 2012, at 21:40, Active
Venture - Tom wrot
> 20-Jul-2012 15:26:40.181 config: error:
> /var/named/etc/namedb/conf/zone_0.conf:1529: zone 'x.net':
> already exists previous definition:
> /var/named/etc/namedb/conf/zone_0.conf:1529
> 20-Jul-2012 15:26:46.270 general: error: reloading configuration
> failed: failure
That looks very suspic
On 12-07-20 07:16 PM, Mark Andrews wrote:
>
> "dnssec-validation auto;"
Well, this seems to have done the trick. Changing it from yes to auto
has eliminated most (almost all in fact) of the validation
warnings/errors I was getting in my logs.
> tells named to use the compiled
>
Hello *,
I have only one fixed IP from my ISP and run my own (Master) name server.
A friend from me in another Network segment does the Slave.
I do the same for him.
Now I am puzzeling arround, whether it is possibel, to setup the slave DNS
to accept any domains (including newly created) from a
> I find it realy annoying, if I have ask every time the owner of the Slave,
> to add a new zone.
Assuming your version of BIND is new enough, look at `rndc addzone' with
which you can add and remove zones at run-time w/out having to edit
`named.conf'.
-JP
On Sat, July 21, 2012 20:03, Jan-Piet Mens wrote:
>> I find it realy annoying, if I have ask every time the owner of the
>> Slave,
>> to add a new zone.
>
> Assuming your version of BIND is new enough, look at `rndc addzone' with
> which you can add and remove zones at run-time w/out having to edit
On 21/07/12 20:03, Jan-Piet Mens wrote:
>> I find it realy annoying, if I have ask every time the owner of the Slave,
>> to add a new zone.
> Assuming your version of BIND is new enough, look at `rndc addzone' with
> which you can add and remove zones at run-time w/out having to edit
> `named.conf
> Which mean, my DNS partner need his own rndc key which let him add/remove
> zones as slave?
You are the master. He is the slave. You have an rndc key for his slave
server, so that you can add a slave zone on his server. [Substitute
he/his by she/hers if required.]
And vice versa. :)
Grab a rec
I have gotten a sugestion which should work very well:
1) NS has apache SSL running
2) Create a script which add/remove zones to/from a "slave zones list"
3) run a cronjob which update the named_slave_zones.conf and reload named
This give me the possibility to create more then one "slave zones
> IIRC that will add the zone to the master, the question, as I heard it,
> was to add it to the slave server, to avoid disturbing the owner of
> the slave to manually editing the slave config.
With `rndc addzone' you specify whether you are adding a master or slave
zone, just as you would in na
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 2012-07-21 at 19:34 +0200, With No Name wrote:
> I find it really annoying, if I have ask every time the owner of the
> Slave, to add a new zone.
Publish the list of zones which your friend should slave. That can be
published any number of way
11 matches
Mail list logo
