Hi Guys

I am using bind 9 for my dns server i did some chnages to one of our customer zone file now i want to force update for my slave dns server how do i do this?

Thanks for your


---------------------------------
Yahoo! Answers - Get better answers from someone who knows. Tryit now.

Hi,

Normally your secondary NS should synchronize by itself after a
certain amount of time. The problem for the slave NS is to know about
changes. In your primary NS, you can add the "notify yes" command in
the zone declaration, so that salve NS (declared in the zone file!)
are notified about changes.
If your slave NS is not declared in the SOA of your zone, you can use
the "also-notify x.x.x.x" parameter.

After doing this, the secondary should synchronise as soon as the
master has reload the updated zone. If it's not the case, you should
have a careful look to the serial number...


regards,
Lionel




david robert <davidforlinux@yahoo.co.uk> a écrit :

> Hi Guys
>
> I am using bind 9 for my dns server i did some chnages to one of
> our customer zone file now i want to force update for my slave dns
> server how do i do this?
>
> Thanks for your
>
>
> ---------------------------------
> Yahoo! Answers - Get better answers from someone who knows. Tryit now.



--
x3n`

--
x3n@molinier.eu
http://www.molinier.eu

thanks for your

x3n <x3n@molinier.eu> wrote: Hi,

Normally your secondary NS should synchronize by itself after a
certain amount of time. The problem for the slave NS is to know about
changes. In your primary NS, you can add the "notify yes" command in
the zone declaration, so that salve NS (declared in the zone file!)
are notified about changes.
If your slave NS is not declared in the SOA of your zone, you can use
the "also-notify x.x.x.x" parameter.

After doing this, the secondary should synchronise as soon as the
master has reload the updated zone. If it's not the case, you should
have a careful look to the serial number...


regards,
Lionel




david robert a écrit :

> Hi Guys
>
> I am using bind 9 for my dns server i did some chnages to one of
> our customer zone file now i want to force update for my slave dns
> server how do i do this?
>
> Thanks for your
>
>
> ---------------------------------
> Yahoo! Answers - Get better answers from someone who knows. Tryit now.



--
x3n`

--
x3n@molinier.eu
http://www.molinier.eu



---------------------------------
Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your freeaccount today.

thanks for your

x3n <x3n@molinier.eu> wrote: Hi,

Normally your secondary NS should synchronize by itself after a
certain amount of time. The problem for the slave NS is to know about
changes. In your primary NS, you can add the "notify yes" command in
the zone declaration, so that salve NS (declared in the zone file!)
are notified about changes.
If your slave NS is not declared in the SOA of your zone, you can use
the "also-notify x.x.x.x" parameter.

After doing this, the secondary should synchronise as soon as the
master has reload the updated zone. If it's not the case, you should
have a careful look to the serial number...


regards,
Lionel




david robert a écrit :

> Hi Guys
>
> I am using bind 9 for my dns server i did some chnages to one of
> our customer zone file now i want to force update for my slave dns
> server how do i do this?
>
> Thanks for your
>
>
> ---------------------------------
> Yahoo! Answers - Get better answers from someone who knows. Tryit now.



--
x3n`

--
x3n@molinier.eu
http://www.molinier.eu



---------------------------------
Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for your freeaccount today.

On 07.08.07 10:42, x3n wrote:
> Normally your secondary NS should synchronize by itself after a
> certain amount of time. The problem for the slave NS is to know about
> changes. In your primary NS, you can add the "notify yes" command in
> the zone declaration, so that salve NS (declared in the zone file!)
> are notified about changes.

> If your slave NS is not declared in the SOA of your zone, you can use
> the "also-notify x.x.x.x" parameter.

wrong. The notify is usually sent to all servers which have NS record,
except the one in SOA. So, put the name of real master into SOA (even if
it's not accessible from the net). don't put name of any slave to SOA.

You can of course override these settings with "notify (yes|no|explicit)"
and also-notify settings in BIND config.

> After doing this, the secondary should synchronise as soon as the
> master has reload the updated zone. If it's not the case, you should
> have a careful look to the serial number...

.... which is a thing people use to forget and then they wonder why it
doesn't work...
--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"To Boot or not to Boot, that's the question." [WD1270 Caviar]


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org