Re: [users] vegadns roadmap for 2006?

[Bill Shupp]

[EMAIL PROTECTED] wrote:

Hello everyone
 
Just a quick note to first, whish you all vegadns fans a happy new year, 
and also to enquire about the possible

evolutions / dev of vegadns.
 
I'm currently still running 0.9.x in production, and have been playing 
with new 1.x builds which look really promising.

I was wondering if Bill had an idea of the future updates/features to come..


There is no "official" road map.  But I suppose it would not hurt to 
draw one up.  I have a 1.1.6 release that I've been working on for a 
couple of months that fixes a lot of problems.  But there's still work 
to be done on logging and the new permissions structure, although most 
areas of VegaDNS now support it.



Also, a while ago in the list i remember some posts about template 
default records per groups, i'm not sure it is planed, but think it 
could have some use, here i'm dealing with small colo service where some 
clients have some servers with their own name servers & own email/web 
servers, others use my own name servers.. In that case it could be neat 
to have the abbility to specify a template of default www.DOMAIN 
 mail.DOMAIN etc to use per group.


This is not in place yet, but I like the idea.  Default records is one 
of the last parts to not support the new permissions structure.


A thing about reverse dns, wondered if they are any plans to 'auto 
create' a reverse PTR record based on an A record. Of course that'll 
mean some check of some kind to ensure that all given IP aren't already 
assigned to another PTR record ..
Also such features might have to be available only by senior admin, but 
delegating the reverses handling to group admins when needed for some 
sets of IP's would sure help too


This is another area.  The idea of having a "check here to create ptr" 
in the A record create screen has been on the TODO list for a while, but 
is a relatively low priority.



Anw, these are just rough ideas i had laying in my head for quite some 
time now.


Thanks for sharing them.  I'll try to get 1.1.6 out later this week so 
people can start testing it.  I'm hoping to get 2.0 out within a month 
or two.


Regards,

Bill

Re: [users] question and request feature

[Bill Shupp]

Andrea Riela wrote:

Hi folks,

first, a question:
why the NS record uses '&', like BIND, and not '.' ?


"." is really just a shortcut to add an NS, A, ans SOA record in one 
shot.  I always found it confusing to add multiple "." records, when you 
only need one SOA record.  Also, when you do axfr-get imports, it uses 
the individual records, I believe.




second, a request for feature:
normally we could use the update-data.sh manually or with crontab. What 
about a "web button" to apply changes?


That would require a setuid cgi or the like to execute it as a user 
outside the web server.  I'm considering a vegadnsd program to handle 
such tasts, as well as other server administration tasks (binding to 
IPs, restarting the server, getting info about uptime, etc...)


Regards,

Bill

[users] vegadns roadmap for 2006?

[r.sand]

Hello everyone
 
Just a quick note to first, whish you all vegadns 
fans a happy new year, and also to enquire about the possible
evolutions / dev of vegadns.
 
I'm currently still running 0.9.x in production, 
and have been playing with new 1.x builds which look really 
promising.
I was wondering if Bill had an idea of the 
future updates/features to come..
 
Also, a while ago in the list i remember some posts 
about template default records per groups, i'm not sure it is planed, but think 
it could have some use, here i'm dealing with small colo service where some 
clients have some servers with their own name servers & own email/web 
servers, others use my own name servers.. In that case it could be neat to have 
the abbility to specify a template of default www.DOMAIN mail.DOMAIN etc to use per 
group.
 
A thing about reverse dns, wondered if they 
are any plans to 'auto create' a reverse PTR record based on an A 
record. Of course that'll mean some check of some kind to ensure that all given 
IP aren't already assigned to another PTR record ..
Also such features might have to be available only 
by senior admin, but delegating the reverses handling to group admins when 
needed for some sets of IP's would sure help too
 
Anw, these are just rough ideas i had laying in my 
head for quite some time now.
 
Take care all of you, and see you in 2006 
;)
 
Rudolph.

[users] question and request feature

[Andrea Riela]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi folks,

first, a question:
why the NS record uses '&', like BIND, and not '.' ?

second, a request for feature:
normally we could use the update-data.sh manually or with crontab. What 
about a "web button" to apply changes?


thanks for your support,
Regards
Andrea
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDsRT9MakHrsrHP9wRAv6xAJ9q7rD23e8FRe8USJTnR+tiJI7kaQCaAtwd
sh/JLyYdxBy8ChMp/aLdvmo=
=hD3E
-END PGP SIGNATURE-