Difference between revisions of "Dhcp-dns"
Unnilennium (talk | contribs) |
|||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 4: | Line 4: | ||
=== Maintainer === | === Maintainer === | ||
[mailto:stephdl@de-labrusse.fr Stéphane de Labrusse] AKA [[User:Stephdl|Stephdl]] | [mailto:stephdl@de-labrusse.fr Stéphane de Labrusse] AKA [[User:Stephdl|Stephdl]] | ||
| + | |||
| + | ===Version=== | ||
| + | |||
| + | {{#smeversion: smeserver-dhcp-dns }} | ||
=== Description === | === Description === | ||
| Line 12: | Line 16: | ||
after that on your network you can ping, ssh a remote host by its name | after that on your network you can ping, ssh a remote host by its name | ||
| − | === Installation === | + | === Installation SME8, SME9, SME10=== |
| − | === | + | |
| − | + | <tabs container><tab name="For SME 10"> | |
| + | yum --enablerepo=smecontribs install smeserver-dhcp-dns | ||
| + | </tab> | ||
| + | <tab name="For SME 9 or SME 8"> | ||
| − | yum --enablerepo= | + | yum --enablerepo=smecontribs 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 30: | ||
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 |
| − | + | </tab> | |
| − | + | </tabs> | |
| − | |||
| − | |||
===How it works=== | ===How it works=== | ||
| Line 39: | Line 44: | ||
ping pc_name | 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. | 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. | ||
| Line 58: | Line 65: | ||
yum remove smeserver-dhcp-dns | yum remove smeserver-dhcp-dns | ||
signal-event post-upgrade; signal-event reboot | signal-event post-upgrade; signal-event reboot | ||
| + | |||
| + | ===Bugs=== | ||
| + | Please raise bugs under the SME-Contribs section in [http://bugs.contribs.org/enter_bug.cgi bugzilla] | ||
| + | and select the smeserver-openvpn-routed component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-dhcp-dns|title=this link}} | ||
| + | |||
| + | |||
| + | {{#bugzilla:columns=id,product,version,status,summary |sort=id |order=desc |component=smeserver-dhcp-dns|noresultsmessage="No open bugs found."}} | ||
| + | |||
| + | ===Changelog=== | ||
| + | Only versions released in smecontrib are listed here. | ||
| + | |||
| + | {{#smechangelog: smeserver-dhcp-dns}} | ||
| + | |||
| + | |||
| + | |||
[[Category: Contrib]] | [[Category: Contrib]] | ||
Latest revision as of 03:36, 31 March 2021
Dhcp-dns for SME Server
Maintainer
Stéphane de Labrusse AKA Stephdl
Version
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 SME8, SME9, SME10
yum --enablerepo=smecontribs install smeserver-dhcp-dns
yum --enablerepo=smecontribs 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
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
Bugs
Please raise bugs under the SME-Contribs section in bugzilla and select the smeserver-openvpn-routed component or use this link
Changelog
Only versions released in smecontrib are listed here.
- moving to systemd + update event [SME: 11031]
- Initial import to SME10 tree [SME: 11031]
- now released in smecontribs
- finished lease are now prohibited
2015/07/25 stephane de Labrusse 1.2.0-1
- enhancement following the bug [SME: 2388]
- e-smith-tinydns-2.4.0_add_hostname_following_dhcpdleases_hostname.patch
