I am not sure what is better (end easier) - import
'generate' (which means 'proceed it at time of import') or
create a spcial, 'GENERATE', RR which generates an entries
when zone is updated? (First is easier).
Let's see, proBIND update is in my TODO list for next 2 months.
Alex Roudnev
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to see this feature too, for the moment I have
a zone which is too big to load for every browser except
lynx, the html is 8+MB and all browsers crash on that.
BTW: it is a great project, thanks a lot
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can see a 3 different issues in this posts:
(1) - import can understand '$GENERATE' and expand it;
looks as it is not a vey good idea;
(2) - very big zone support. It is known problem, I have a
data base editior(s) which supports paging thru the data,
and allow to restrict the size of information on the screen.
(3) - $GENERATE pseudo record, which generates real RR's
only when zone is created for the server.
Alex
(3) - most likely, will be implemented on the next iteration;
unfortunately, I can not schedule time for next release (I
plan small release to include small patches and CNAME
control, and may be better user's control.
Give me an example(s) of 'GENERATE' which youy have /
would like to have. I have not such things in my installation
(s), so I do not want to implement something complicated,
but it can be easy to implement simple 'generate' record.
Problem is, that it is not single change - generated records
must appear not only on 'update', but on some other
operations (such as IP space browsing) as well.
So, let's see an examples first.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=680290
I am not sure what is better (end easier) - import
'generate' (which means 'proceed it at time of import') or
create a spcial, 'GENERATE', RR which generates an entries
when zone is updated? (First is easier).
Let's see, proBIND update is in my TODO list for next 2 months.
Alex Roudnev
Logged In: NO
I would like to see this feature too, for the moment I have
a zone which is too big to load for every browser except
lynx, the html is 8+MB and all browsers crash on that.
BTW: it is a great project, thanks a lot
Logged In: NO
Let's clarify, what we are talking about.
I can see a 3 different issues in this posts:
(1) - import can understand '$GENERATE' and expand it;
looks as it is not a vey good idea;
(2) - very big zone support. It is known problem, I have a
data base editior(s) which supports paging thru the data,
and allow to restrict the size of information on the screen.
(3) - $GENERATE pseudo record, which generates real RR's
only when zone is created for the server.
Alex
(3) - most likely, will be implemented on the next iteration;
unfortunately, I can not schedule time for next release (I
plan small release to include small patches and CNAME
control, and may be better user's control.
Give me an example(s) of 'GENERATE' which youy have /
would like to have. I have not such things in my installation
(s), so I do not want to implement something complicated,
but it can be easy to implement simple 'generate' record.
Problem is, that it is not single change - generated records
must appear not only on 'update', but on some other
operations (such as IP space browsing) as well.
So, let's see an examples first.
Logged In: NO
In the function perform_rr_action($input)
...
default:
...
if($input["type_$id"]!='GENERATE_A' && $input["type_$id"]!='GENERATE_P')
$warn = validate_record($input['zone'],
$input["domain_$id"], $input["ttl_$id"],
$input["type_$id"], $input["pref_$id"],
$input["data_$id"]);
...
IN the function add_record($INPUT_VARS)
...
if($type!="GENERATE_A" && $type!="GENERATE_P")
$warnings = validate_record($zone, $domain, $ttl, $type, $pref, $data);
...