2020-03-27 21:44:56 +01:00
Create DNS records for DHCP leases
==================================
2024-03-06 14:30:18 +01:00
[](https://github.com/eworm-de/routeros-scripts/stargazers)
[](https://github.com/eworm-de/routeros-scripts/network)
[](https://github.com/eworm-de/routeros-scripts/watchers)
2024-04-04 21:45:02 +02:00
[](https://mikrotik.com/download/changelogs/)
2024-03-06 14:30:18 +01:00
[](https://t.me/routeros_scripts)
[](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick& hosted_button_id=A4ZXBD6YS2W8J)
2023-01-10 14:45:27 +01:00
[⬅️ Go back to main README ](../README.md )
2020-03-27 21:44:56 +01:00
2022-02-12 13:05:56 +01:00
> ℹ ️
2022-02-11 23:34:39 +01:00
> installation. See [main README](../README.md) for details.
2021-05-03 15:07:50 +02:00
2020-03-27 21:44:56 +01:00
Description
-----------
2023-03-25 22:51:33 +01:00
This script adds (and updates & removes) dns records based on dhcp server
leases. An A record based on mac address is created for all bound lease,
additionally a CNAME record is created from host name if available.
2020-03-27 21:44:56 +01:00
Requirements and installation
-----------------------------
Just install the script:
$ScriptInstallUpdate dhcp-to-dns;
Then run it from dhcp server as lease script. You may want to use
[lease-script ](lease-script.md ).
A scheduler cares about cleanup:
2022-05-11 10:02:15 +02:00
/system/scheduler/add interval=15m name=dhcp-to-dns on-event="/system/script/run dhcp-to-dns;" start-time=startup;
2020-03-27 21:44:56 +01:00
Configuration
-------------
2020-06-02 22:05:21 +02:00
On first run a disabled static dns record acting as marker (with comment
"`--- dhcp-to-dns above ---`") is added. Move this entry to define where new
entries are to be added.
2023-04-13 00:32:13 +02:00
The configuration goes to dhcp server's network definition. The domain is
used to form the dns name:
/ip/dhcp-server/network/add address=10.0.0.0/24 domain=example.com;
A bound lease for mac address `00:11:22:33:44:55` with ip address
`10.0.0.50` would result in an A record `00-11-22-33-44-55.example.com`
pointing to the given ip address.
Additional options can be given from comment, to add an extra level in
dns name or define a different domain.
/ip/dhcp-server/network/add address=10.0.0.0/24 domain=example.com comment="domain=another-domain.com, name-extra=dhcp";
This example would result in name `00-11-22-33-44-55.dhcp.another-domain.com`
for the same lease.
If no domain is found in dhcp server's network definition a fallback from
`global-config-overlay` is used. This is the parameter:
2020-03-27 21:44:56 +01:00
* `Domain` : the domain used for dns records
2023-06-07 14:12:46 +02:00
> ℹ ️
> [`global-config`](../global-config.rsc) (the one without `-overlay`) to
> your local `global-config-overlay` and modify it to your specific needs.
2023-03-25 22:33:02 +01:00
### Host name from DHCP lease comment
Overwriting the host name from dhcp lease comment is supported, just add
something like `hostname=new-hostname` in comment, and separate it by comma
from other information if required:
/ip/dhcp-server/lease/add address=10.0.0.50 comment="my device, hostname=new-hostname" mac-address=00:11:22:33:44:55 server=dhcp;
Note this information can be configured in wireless access list with
[dhcp-lease-comment ](dhcp-lease-comment.md ), though it comes with a delay
then due to script execution order. Decrease the scheduler interval to
reduce the effect.
2020-03-27 21:44:56 +01:00
See also
--------
* [Collect MAC addresses in wireless access list ](collect-wireless-mac.md )
* [Comment DHCP leases with info from access list ](dhcp-lease-comment.md )
2021-05-17 16:32:07 +02:00
* [Create DNS records for IPSec peers ](ipsec-to-dns.md )
2020-03-27 21:44:56 +01:00
* [Run other scripts on DHCP lease ](lease-script.md )
---
2023-01-10 14:45:27 +01:00
[⬅️ Go back to main README ](../README.md )
[⬆️ Go back to top ](#top )
