Difference between revisions of "Dhcp-dns"
Line 13: | Line 13: | ||
=== Installation === | === Installation === | ||
− | |||
− | |||
− | yum --enablerepo=stephdl | + | |
+ | yum --enablerepo=stephdl install smeserver-dhcp-dns | ||
You will then need to activate the database changes etc. | You will then need to activate the database changes etc. | ||
Line 23: | Line 22: | ||
signal-event post-upgrade; signal-event reboot | signal-event post-upgrade; signal-event reboot | ||
or if you do not want to restart your server | or if you do not want to restart your server | ||
− | signal-event dhcp-dns ; | + | signal-event dhcp-dns ; config set UnsavedChange no |
− | |||
====For SME9==== | ====For SME9==== |
Revision as of 22:13, 19 August 2015
Dhcp-dns for SME Server
Maintainer
Stéphane de Labrusse AKA Stephdl
Description
This contribution for SME Server adds the abilities to parse the dhcpd.leases file and feed the data (the name of the computer) into tinydns (the dns server). Original idea from bugzilla:2388
It gives a real dns name to computers on your network instead of the dummy name
pc-00001.mycompany.local
after that on your network you can ping, ssh a remote host by its name
Installation
yum --enablerepo=stephdl install smeserver-dhcp-dns
You will then need to activate the database changes etc. The 'official' way is to perform
signal-event post-upgrade; signal-event reboot
or if you do not want to restart your server
signal-event dhcp-dns ; config set UnsavedChange no
For SME9
This feature could be imported soon directly in sme9, this is pending you work in bugzilla: 2388
How it works
Of course all is done by a dhcp service so you need to set up one and play with other computers
If all is ok then you may be able to see the name of your computer in the tinydns record
less /var/service/tinydns/root/data
Then you can ping your host by their name directly in your sme console, test it
ping pc_name
or
host pc_name
if it doesn't work you can take a look to the dhcpd.leases to see if your host is well written in that configuration file with a correct dhcp lease.
less /var/lib/dhcpd/dhcpd.leases
for example with that kind of records (binding state active;):
lease 192.168.151.69 { starts 1 2014/07/28 07:26:59; ends 2 2014/07/29 07:26:59; binding state active; next binding state free; hardware ethernet 00:1e:8c:ad:7d:d6; uid "\001\000\036\214\255}\326"; client-hostname "infob14";
Uninstall
yum remove smeserver-dhcp-dns signal-event post-upgrade; signal-event reboot