linuxconf all changes logs

linuxconf all changes logs

Change log index

Version 1.13r14


Stuff DNS reverse zone at creation time

When you create a new DNS reverse zone (, the dnsconf module walks all the other zone and preset this new zone. After that dnsconf will maintain the reverse mapping transparently, as it has always done. This is handy as we generally "learn" about those reverse zone well after the DNS is created :-)

Version 1.13r15


Delete DNS domain from the command line

You can now delete a domain by using the following command

/sbin/dnsconf --deldomain domain

HINFO and RP records now supported in DNS

The dnsconf module has never supported those records and was complaining when one was adding those by hands. It is fixed.

Version 1.13r15.1


The TXT record now supported in dns zone files

Another record (TXT) is now properly managed by the dnsconf module. While you can edit those records from Linuxconf, you can enter those records if you need in the various zone file.

Version 1.14r2


dnsconf: more support for bind8 features

The following features are now supported (you can set them from the user interface):

  • Access control lists (acls). Thanks Mathieu...
  • option allow-query
  • option allow-transfer
  • option listen-on
  • zone allow-query
  • zone allow-update
  • zone allow-transfer
  • zone also-notify
  • zone notify flag

Further, unknown directives (Unmanaged by Linuxconf) are properly stored and rewritten back. I hope that this module will finally please all bind8 users... Check it out!

Version 1.14r3


dnsconf: notify field handling

dnsconf was not handling the notify field properly. You can now set the general behavior in the feature screen. You can edit this for the zone for now, but you can set it manually and your setting will be preserved, including the absence of setting (inherit the default).. Thanks Matthieu!

Bug fixes

dnsconf corrupting SOA records

Because of a bug in misc/ and misc/, the various parameters of the SOA records were reset to 0. This is fixed.

dnsconf: IP allocation range

Because of the same bug related to the SSTRING, dnsconf always reports an invalid range syntax.

Version 1.14r3.1


dnsconf: setting the notify field for primaries

A new field allows you to set the notify field of a zone to either no, yes or default. When set to default, you inherit the global setting you can already configure with 1.14r3.

Version 1.15r0.1

Bug fixes

Some parsing problem in /etc/named.conf

The way I was managing the "unknown to Linuxconf yet" directive in /etc/named.conf was inaccurate and causing a segfault.

Version 1.15r0.2


rework for secondaries

Mathieu have reworked dnsconf a bit to allow previewing of the secondaries. You can now configure access control for slave zones as well.

More work is needed on the user interface side though.

Version 1.15r0.3


dnsconf enhancement

Various enhancements were done to dnsconf since 1.15. A major rework of the zone file management (master and slave) has been done by Mathieu. This allows dnsconf to deal with secondary in the same way internally as primaries, in read-only mode. The visible parts are

  • The secondary menu presents the revision date, as read from the SOA record, like the primaries. This is handy when you want to know if the secondary is up to date.
  • In the secondary dialog, there is an preview button. You can look at the domain definition.
  • There is an update button. This trigger a zone transfer. This is handy when you want to make sure a secondary is up to date.

In the future, you should be able to

  • Browse the various records
  • Switch a secondary (slave) to primary (master)

Version 1.15r2.3

Bug fixes

dnsconf: Problems with comments breaking SOA records

There was a problem in the parsing of zone files. The SOA record was not parsed properly and this was creating corruption in the timing section (features part of the dialog).

Version 1.16r1


forward zone in dnsconf

This feature is now supported. This allows one to selectively support a zone or forward resolution to another DNS.

Version 1.16r1.1

Bug fixes

dnsconf: ttl fields not optional

The various TTL fields in a domain definition (refresh, retry) can't be empty anymore.

Version 1.16r1.3


dnsconf: new command line

I have added a new command line option to dnsconf

/sbin/dnsconf --delsecondary domain

which ... does what it does :-)

Version 1.16r1.4

Bug fixes

dnsconf: Finding first available IP

An old limitation of dnsconf was removed. When computing the first available IP (IP allocation space), it was not processing IP reverse mapping zone. So for DNS hosting some reverse zone, but not the corresponding domains, dnsconf was proposing not reliable (the available IP was not so available).

Version 1.16r6.1


dnsconf: MX with same priority

A small trick was added to the MX field. If you specify several host on the same line in the dialog, they will get the same priority.

Bug fixes

dnsconf: time in the SOA records

The various time to live in the SOA records may be encoded in seconds, hour, days and week. Linuxconf was not supporting those suffix properly, turning everything into seconds. Fixed!

Version 1.16r7


Module dnsconf: syncing basic host information and DNS

Linuxconf normally update the DNS from the information found in the basic host information dialog. This is generally a good thing. Some people have problems with this and wish to present information unrelated to the basic host information. I have added a check-box in the feature dialog to disable this feature. On by default.

Version 1.16r10

Bug fixes

Module dnsconf: parsing ip/subnet

There were two bugs corrected in 1.16r10. Some network definition where not parsed properly. the syntax network/subnet was only accepted in some condition. This has been generalized.

The listen-on global option directive was not parsed properly when the optional port was specified.

Version 1.17r1

Bug fixes

Module dnsconf: include files in named.conf

Include file were supported, but it was broken (Linuxconf was crashing). This is fixed minimally: Linuxconf knows how to read the include files but can't write them back, so everything is merged in /etc/named.conf.

Include file may be organized arbitrarily. Rewriting them exactly is not an easy job.

Version 1.17r8

Bug fixes

dnsconf was crashing with some invalid named.conf

/etc/named.conf with unbalanced braces were causing troubles. Fixed!

Version 1.18r7


Module dnsconf: Support for $ttl directive

The module now understand the $ttl directive in zone file. You can set it from the zone creation/edition dialog in the feature section.

Version 1.19r1


Module dnsconf: reloading instead of restart

On some distributions, Linuxconf issues itself the reload or restart for various services. For named, Linuxconf used to stop and start it. It now sends a signal. Please test this (on SuSE for one).

Module dnsconf: support for ! in named.conf

The negation (! character) is now supported in named.conf lists.

Version 1.20

Bug fixes

Module dnsconf: parsing of chaos, hs and hesiod keyword

The zone class in named.conf was not properly parsed.

Version 1.20r1


Module dnsconf: adding comments to zone

For every zone, you can enter 4 lines. They are stored in /etc/conf.linuxconf. Those lines are:

  • Administrator
  • General comment
  • Renewal date
  • Registrar

Bug fixes

Module dnsconf: data class

Some data class were not supported in /etc/named.conf. Now in, chaos, hesiod and hs are managed.

(ed. note: A little note. 1.20r1 has a glitch there, do not use it for dns. Use 1.20r2)

Version 1.20r2

Bug fixes

Module dnsconf: bug while creating a new zone

A bug was introduced in 1.20r1 (support for data class chaos and friends). At zone (domain) creation time, an uninitialized variable is causing some garbage in /etc/named.conf. Ultimately, Linuxconf may crash while rewriting the file, producing a truncated file. 1.20r2 fixes this!

Version 1.21r3


Module dnsconf: new --newsecondary command line

The --delsecondary was there, but the reverse was missing!

Module dnsconf: template domain

In the feature dialog, you can specify the name of the default or template domain. This domain (it has to exist in the DNS) will be used when creating a new domain. The module used to compute default values but could not guess stuff like secondaries and backup MXs.

Now, when you create a new domain, it will copy many settings from the template zone if defined. This affect the interactive and command line mode.

The following command line still work:

	/sbin/dnsconf --newdomain new_domain template_domain

but if you omit the template_domain argument, then the one specified in the features dialog will be used. This should ease your work a bit.

Module dnsconf: update zone files as needed

The module used to write back zone file every time a change was made anywhere. So zone file were needlessly rewritten back and named was sending a update to every secondary for nothing.

Now a zone is updated only if it was changed.

Version 1.21r4

Bug fixes

Module dnsconf: segfault while creating a domain

The new template domain feature introduced in 1.21r3 broke a few things and it was not possible to create a new domain interactively.

Version 1.21r6

Bug fixes

Module dnsconf: case insensitive

Some string compare were done case sensitive and named.conf is case insensitive.

Version 1.21r8


Module dnsconf: more validation

The module does some sanity check on the value of the "directory" directive to make sure it exists. Bad thing was happening if this was not the case.

Version 1.22

Bug fixes

Module dnsconf: two update in a row

The enhanced made to only update the zone file which were effectively changed triggered a bug-let where subsequent changes were not saved to file. Fixed!

Version 1.23

Bug fixes

Module dnsconf: few fixes

The # character was not parsed properly in named.conf. When creating a new zone, the dot was not added in some fields.

Version 1.23r2

Bug fixes

Module dnsconf: keyword key

The "key" keyword was not supported in the access control specifications.

Version 1.24


/var/named/sec permissions

In newer distributions, named is run as user named, not root anymore. The dnsconf module creates secondaries in /var/named/sec. This directory was owned by root. It will be owned by named.named from now on. On older distribution, Linuxconf will still create it as root.root though.

Module dnsconf: sorting

Domains and secondaries are always sorted in the interface, but the order in named.conf is not changed.

Version 1.24r4


Module dnsconf: reverse for sub-nets

The module now implement a scheme to delegate sub-net reverse mapping. This is new and experimental. When you create a reverse zone,there is an extra field to enter the sub-net. You enter the last digit of the network address and the number of significant bit. From there, Linuxconf will know how/when to update this reverse zone.

For example, if you have the sub-net you would enter:

	Network number: 192.168.1
	Subnet x/y         : 64/26

The zone created will be called 64/ The owner of the zone will have to set a bunch of cnames to point his DNS to yours.

Version 1.24r8


Module dnsconf: edit the ttl field

The module has been reworked a bit so you can set the ttl on various records. This include the A, MX and NS records. The dialogs have been enhanced to present this extra field in various place. It is optional.

Module dnsconf: many MX and NS record

The was only allowing 3 NS and MX records. Well, it was supporting more, but passed this limit, you were not able to add using Linuxconf. You were able to edit the 4 you had already, but not to add a fifth one for example. now Linuxconf insure there is an extra empty field at the end of the form.

Bug fixes

Module dnsconf: time to live bug

The time to live in zone file was not properly supported. It was only handling numeric value and was confused by the letter suffix (D for day, H for hour, ...). This is fixed.

Version 1.24r9


Module dnsconf: classless reverse mapping, take 2

The solution to support classless IP reverse mapping delegation was not flexible enough and was not working in some case (though it follows the latest RFC). It was using sub-nets. Now it is using range, so it is much more flexible. Consider this work in progress.

When you create a new reverse zone, you can enter a range using the x-y syntax. that's it. From now on, Linuxconf will update the the zone if the IP number fits in that range. The zone will be named

for a a.b.c network.

Version 1.25


Module dnsconf: interactive updates from network config

The DNS was automatically updated from the basic network configuration. In general, this was a good thing, Now it is interactive with a yes/no box.

Version 1.25r3


Module dnsconf: allow-recursion supported

It is possible to handle this topic. It controls who can use your named server to request information it does not already know.

Bug fixes

Module dnsconf: classless delegation

There were some bugs in the newly added classless reverse zone delegation. The NS records were not properly handled.

Version 1.25r7

Bug fixes

Module dnsconf: updating the DNS from the host configuration

The module has done that for a long time, but in some case it was claiming to update the DNS even if there were no domains matching the host configuration. Fixed!

Version 1.26r2


Module dnsconf: more command lines

The module has now the --unsetmx, --unsetns and --unsetcname command line option, to make it more complete.

Module dnsconf: zone transfer

The module now support the bind 9 style (using rndc) as well as the other named-xfer program.

Version 1.26r3

Bug fixes

Module dnsconf: secondary zone with many primaries

The dnsconf module was limiting secondary zones to 4 primaries. There is no limit now.

Version 1.28r2


Module dnsconf: more validations

When entering IP numbers, more validation are done. Also, if you have defined some "IP allocation spaces", the IP numbers are checked to see if they fit in one of the ranges. A warning is issued if not. The idea is to uncover some potential errors (You typed a valid IP, but in a wrong IP network for example).

Version 1.28r3


Module dnsconf: virtual registry enhancement

The domain definition dialog is now available using the virtual registry. You can now do things like

	/sbin/vregistry --set primary.ns1.some_domain

Or you can change major updates using little scripting

	for domain in `vregistry --getvalue`
		/sbin/vregistry --set primary.ns1.$domain

Version 1.29

Bug fixes

Module dnsconf: TTL parsing

There was a flaw when parsing TTLs (time to live) and the SOA records refresh times when the minute suffix was used (M). The other (H for hours, W for weeks and D for days) were properly supported. Linuxconf was properly encoding the suffix, but not properly parsing it back. Minutes were changes to seconds... You may want to review your SOA records (domain definition, features, ...).

Version 1.29r1


Module dnsconf: using the virtual registry

The module has been enhanced to support the virtual registry. You can use it to configure and populate DNS domains. You use the variables primary.*.domain and dnsconf.*.host to manage the DNS.

The module had already extensive command lines. But the virtual registry offers a fine grain approach allowing you to setup more stuff from the command line. Here are few example:

  • Retrieving the list of domains currently configured

    /sbin/vregistry --getvalue

  • Creating a new domain

    /sbin/vregistry --set \ \ \ \

Version 1.29r3


Module dnsconf: more virtual registry

The module now export all the access control stuff to the virtual registry. Also, secondary are fully configurable using the vregistry as well.