I checked what happens if I set
option domain-name "linuxmce.lan";
in the /etc/dhcp3/dhcpd.conf file.
After that I can actually resolve http://dcerouter
on my laptop, so that looks good.
I now know what changes should make to the config files, now it is a matter of getting the LinuxMCE code to do that.
I saw that the domain name is also configurable in the web-admin, so I figured it would be a good first step to add the domain name to the DHCP template file, and after that create a template for the bind files.
The dhcp template contains several keys like %CORE_INTERNAL_ADDRESS%, so I wanted to check where this template is filled in and see if there is already a key for the domain name. If that would be the case the DHCP changes would be a simple matter of updating the template.
However, it seems that the template is not used; my search lead me to PlutoDHCP.cpp file in the source code, and that source code contains a function that produces the text for the dhcpd.conf file from scratch. The output of this function seems to be the same as the template (except for the comments on the first 3 lines), but it does not actually use the template at all.
I guess that means I should not alter the template but just the PlutoDHCP.cpp file, or am I missing something?
Anyway, is there an example of how the template files should be used? I saw that the ddclient.conf.template is filled in the DynamicDNS.sh script. I can create a similar approach for the bind9 config files (shell scripts that use the ReplaceVars function), if that is the proper way to go.