Home Virtualisation Market linux.conf.au finally controls domain name
It's taken several years, quite a lot of negotiation and the use of alternatives to get it through an uncertain period. But Australian open source conference Linux.conf.au has finally permanently secure the rights to its own domain name.

The domain appears to have been registered back in 2001, when Australia's internet was in its infancy and much of the nation's domain name registration control was still handled by Melbourne University technician Robert Elz. At that point, it was envisaged that conferences would use the .conf.au extension to host their own web sites, much as companies used .com.au and educational institutiions .edu.au.

However, although much of the domain responsibilities were transferred over the years to organisations such as AusRegistry and .au Domain Administration (auDA), as late as 2008, the .conf.au space was still controlled by Elz, and the first outage hit the conference's site.

Then in 2009, auDA, which now regulates Australia's domain space, cast the future of the domain further into doubt with a vote being held by the organisation to kill the .conf.au and .info.au spaces permanently. At that stage the conference, which is run by Linux Australia, started using a number of other temporary domain names for its yearly conference '” such as http://lcaunderthestars.org.au for the upcoming conference in Ballarat in January 2012.

However, in an email to the Linux Australia mailing list last week, the organisation's president John Ferlito finally laid rest to the problem permanently, noting that the conference had established 'a long-standing online identity through the use of linux.conf.au' and that there was a strong view for keeping the domain around '” 'grandfathering it' as an exception to the normal rule.

'So I'm very pleased to announce that, from this point onwards, the linux.conf.au domain will be available all year round, rather than the somewhat traditional six monthly on/off cycle that many conference regulars have become familiar with,' wrote Ferlito.

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Connect