I have compiled (and yes it did take me a long time) a list of known problems and bugs encountered with the new DOMAINZ registry system. It stands at 49 at present. Many of them have now been resolved but I believe it is important to note them as they occurred.

The list is at http://www.dpf.ac.nz/isocnz/domainz.htm

Excellent idea - I can see this list growing rapidly as more people add issues to the list. I think it's safe to say that Domainz are unaware of many of the problems with their system, and so it is important for us to (politely) raise these issues. A buglist such as this one is an ideal way to do so. Here's my contribution: i. The Delete User button on the staff maintenance does nothing at all. ii. The Staff Edit page has garbage characters in the first password box, and nothing in the second. This is a problem, as if an administrator wants to change any of the other details for a staff account, the password must be entered again. This password will not always be known or on hand. Perhaps the password changing functionality should be moved to it's own dedicated page? iii. There is no description of the Facilities avalible in the Role Management page. If you want to create a role that can do a specific task, it may be a matter of trial and error to play around with the faclilities list. iv. There isn't really any documentation at all! v. The only info on the site about the new email template format cannot be found when you are logged in. Instead you must "Exit the site" (log out) and follow the "May 2000 Changes" link on the homepage. Most of the way down the page is a link to a PDF document detailing the new template. Problem is - we can't select and copy text out of the PDF file, so any templates need to be typed by hand!!???! BTW, if anyone has been trying to find this info, the PDF file is at http://www2.domainz.net.nz/registration/NewSystem/DRS-Registrar-D-Technical-... vi. Does the email registration process actually work?? I've only ever seen error messages come back from the parser - never a successful registration message. vii. The email parser at one point was complaining about the applicant_id and/or applicant_password fields being incorrect. These were correct, and I was able to log into the Domainz site using them. The account only had one role assigned to it - that of "Email Interface Access" (sounded like the correct role for an email template account to me, but there isn't any documentation about it!). I then added "Nameholder" and "Registrar Only Function" to the list of roles, and I have not seen any more password error messages. One can infer from this that the problem was in fact a lack of access to the correct role, not a password problem. Why did the error email not specify this?? viii. There is still no clearly defined method for ISPs to transfer the delegation of a zone to themselves without involving actions on the name holder's part. Most name holders don't even know what a domain name is, and have absolutly no interest in trying to figure out the Domainz web site simply because they want to change ISP. How many other registras have had problems moving zone delegations to themselves? Boy - bit more of a rant than I thought I'd do. :) Still, it's all important stuff that Domainz may simply not be aware of, so this is a necessary process I'm afraid. ....of course, the vast majority of these errors should never have made it into the live system in the first place. What sort of testing was done on the system?? Cheers, -h -- Hamish Guthrey hamish(a)asiaonline.net Asia Online (New Zealand) Limited www.asiaonline.net Ph: +64-9-363-0800 Fax: +64-9-363-0801 Snail: PO Box 6721, Auckland, NZ ICBM: 36.50.903S 174.45.975E "The Kernel, the Libraries and the Utilities together are the Distribution, the one Penguin in many forms, forever and ever praised." -- The Gospel of Tux (v1.0) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog