Lukas, do you think that in yast it could work the same way? I don't know the
dns-server module...

Thanks for this information about a tool for editing a DNS zone.

Today it is too late to add a new package into the SL 10.0. Also it would need
more investigation and testing, but the first we would need was a "Feature
Request" -> SLES 10.
Note: DNS Server API2 has a function AddHost() which adds the "A" record and
also the "PTR" record if the reverse zone exists. Unfortunately the UI was not
prepared for that.

Richard: Could you, please clearly define why do you need to create reverse zone
from the zoe file and also whether you wanted to use the dnsedit tool for that
just because the YaST DNS Server module didn't offer that functionality? It is
just to define the Feature Request.

Thank you

I would likt to manage the /forward/ ("A") records and their opposite reverse 
("PTR") records at once.  For a DNS admin this good save a lot of time, 
for a DNS beginner it would make DNS much easier to configure correctly! 
 

Stano: There is a feature request for managing the /forward/ and /reverse/ zone
at once. It should save the time and also minimize inconzistences when user
wants to change one record in two zones.

It would be possible to do it in many ways, at least three:

1.)
a.) Create forward zone (example.org.)
b.) Create reverse zone with disabled editing and link it with the forward one.
c.) When changing the forward zone, change also the reverse records

2.)
a.) Create forward zone (example.org.)
b.) Select some checkbox which would say: [x] Generate also linked reverse zone
or something like that
c.) When saving the forward zone, generate a reverse one from it

3.)
a.) Create forward zone (example.org.)
b.) Create reverse zone (.in-addr.arpa.)
c.) Link these two zones together (some kind of combobox?)
d.) Change also the reverse record in reverse zone when changing the forward
record in forward zone
e.) The same but upside down ;)

Stano: Could you, please, add such feature request into the FeatureDocument? Do
we want it? This functionality exists already in the new DnsServerAPI module but
it is not used by UI.

Just tested that it could work also when we have more forward A records, which
would generate more reverse records, which would work ;)
~~~
A host1.example.org. -> 192.168.0.1
A host2.example.org. -> 192.168.0.2
~~~
PTR 1.0.168.192.in-addr.arpa. host1.example.org.
PTR 1.0.168.192.in-addr.arpa. host2.example.org.
~~~

errrr...

~~~
A host1.example.org. -> 192.168.0.1
A host2.example.org. -> 192.168.0.1
~~~

never mind ;)

All current enhancements should be changed to -> LATER
I'll reopen them after the time comes.

Reopening.
It seems that this feature might be done "automagically".

LATER again, there more important things than DNS Server now.

mass reopening all 10.2 LATER+REMIND bugs.

close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it.