Dixie: DNS and DHCP Config Tool / News: Recent posts

Nothing new in this release. Few bugs are fixed and XML is no more supported.

We have opened the new site for Dixie. Here I want to thank my friend Andreas Kneiseler for making this possible. He is running the site and he has installed everything what is needed for it.

If you visit the site, you will see that it is not filled with data yet. This is what we have to do next, and Andy and me are going to do it as soon as we find some information that has to be published there. We will try to make better manual and put it there. We will publish all news about Dixie and everything there. Only download section will stay at Sourceforge.... read more

As announced in one of previous news postings, this "release" is used to plan and start migration for all of you who have been using Dixie. As you know, Dixie was using XML database to store your data, and we are now moving to SQL only. Therefore, you can use this intermediate version to migrate your data. Read more in Docs section...

Dixie will not support XML based database any more. From now on, we will make all corrections and new code only for MySQL and other databases which Dixie is going to support.
In the following weeks you will find both XML and SQL code if you are synchronizing via CVS. Next Dixie release will be without XML.
So, if you plan to upgrade to future releases, please be ready and fill the data from XML to SQL database prior to upgrading. The tool for this is available in SQL Admin section in current Dixie version. Or you may do it manually. You may find the structure definitions for the tables in template directory.

As more and more users are asking for Dixie and some features I have decided to invite another developer to work on Dixie with me. Andreas Kneiseler is the one and you probably know him from the mailing list. I hope that we will solve problems and develop Dixie faster and better.

Tomica

SRV and NAPTR records are now supported via CVS

It has been almost a year since I haven't uploaded the new "release". Everything is available via CVS, but some people asked me when do I plan to upload something new. Here it is for all of you not using CVS. You may read a little about this "release" in Docs section.

As my friend (dbunic) will code something for Dixie, the latest version is now available via cvs. From time to time we will produce new releases as I did before, but you may use cvs also.

- multihomed DHCP failovers now supported
- few bugs in mysql section solved

Fixed some bugs regarding zone types and DDNS updates

- bugs fixed
- dhcpd hardware type added

Maps included and now working. Read more in Docs section.

Locations are now in external database, MySQL is supported now only. You can filter records from this database to be displayed using 'condition' field in global config. Enter something like "filed='value1' OR field2='value2' OR field3='something else'" as condition.

Please read about it in Docs section

Fixed some problems regarding mysql support.
Cleaned old code garbage.

The MAC field is now multiline and you can enter multiple macs for host. I didn't test this much :-P
Few old bugs are solved.

Now you can locate MAC address from Dixie host database or active leases browser on LAN switches in your enterprise.
You have to enable SNMP option in php (use --with-snmp while compiling php).
Enter all the LAN switches (Cisco) in the LAN switches database. The read community is enough for now.

After that you can run MAC locator from the menu or active leases browser.

Difference:
If it is run from menu it will scann vlans specified for each switch.
If started from leases browser it uses vlan option from the subnet specification (new option in subnet spec). If there is no vlan associated with the subnet then it scanns all vlans specified for the switch.

If you have AD active in some DNS zones, you can compare computer database from AD with the database in Dixie. I think it might be useful. Dixie uses LDAP to connect to AD database. For this to work you must enter LDAP server information in zone details for zone that contains AD. You may use any AD DC as a LDAP server. Valid username/password from your AD is needed to access database. And one more thing; you have to enter baseDN for LDAP search (CN=Computers,DC=yourdomain,DC=com).

Multiple failover servers can now be configured. The primary dhcp server is the one running dixie. Failover servers are defined for each subnet.

Major bug in failover configuration is now solved

Live browsers for DNS records and DHCP leases now works fine

The bug in creating access list for AD controllers is now fixed. IP or server name can now be used.