problem with bind9, view and nsupdate
Michael Dosser
mic at strg.at
Wed Aug 3 08:21:50 UTC 2005
Hi,
Sten Carlsen wrote:
> You have to see the two views as separate nameservers, so what will
> update the external view or tell it:
> 1- there are new data from nsupdate (which is not really true, nsupdate
> has updated the other view (server))
> 2- where can they be found?
Ok.
> The first question could be solved by rndc.
If I got you right you would suggest me to do:
$ rndc reload blasdf.at IN external
This will unfortunatly not work, since blasdf.at is a dynamic zone.
Could you explain more detailed what your suggestion would be?
> The second question is important, where is this information stored? in
> the inside RAM-based data of the internal view. There is no place that
> the external view can see the new info, even if it was aware that it
> existed.
How would I tell nsupdate to update the external view as well? Currently
I'm using the following steps:
$ nsupdate -k /path/to/Kupdatekey -d
> server <ip-address-of-ns1>
> zone blasdf.at
> update add blabla.blasdf.at 86400 A 192.168.0.10
>
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 4646
...
...
Have I overlooked something in the manpage of nsupdate?
Thanks for your help,
Michael Dosser
--
> Please specifically define where data goes that is sent to /dev/null
[...]
Answer 2. All the data goes into another dimension, and comes out of
/dev/random. Stephen Montgomery-Smith on freebsd-hackers
More information about the bind-users
mailing list