DDI?

[Scott Bonikowske]

https://wiki.teemip.net/doku.php?id=start

With its DNS Management and its DHCP Management extensions, TeemIp is definitely part of the DDI world…

So, I keep seeing this is an IPAM/DDI solution. Does it have its own DHCP/DNS servers? Does it have extensions that actually manage (add/remove/update records and configurations) DNS/DHCP servers?

I have been searching around trying to figure out how to create/manage a DHCP server. I can see creating scopes etc, but it looks like it's just for monitoring not for actual lease handling.

Is there something else I am missing?

I am really looking for something like infoblox that is a full DDI but affordable for a home lab, and this keeps coming up,

Thanks!

[Xtophe38]

Hello,

Well, even if TeemIp offers some DDI capabilities, it is not (yet ?) a comprehensive solution that fuels its own DHCP or DNS servers, like EfficientIp, BlueCat or Infoblox could do. It's true that it is not the same price either ;-)

What some people do is use the TeemIp DHCP and DNS management extensions to store information that it is used by scripts to build dhcpd or named configuration files.

Cheers,

[Aas]

Sorry for the late response, but let me add my 2 cents. How I use it with Kea DHCP server.
Kea is pulling the data from TeemIP server via REST/API with this simple cron job:

#!/bin/ash
APIURL="http://teemip.example.com/webservices/rest.php"
DATA='{ "operation": "core/get","class":"PC", "key": "SELECT PC", "output_fields":"name,macaddress,ipaddress_id_friendlyname"}'
RES="/etc/kea/reservations"
alias query='curl -s -X POST  -F "version=1.2" -F "auth_user=rest" -F "auth_pwd=$(cat /etc/kea/user-rest.pw)" $APIURL -F "json_data=$DATA"'
rest (){ query|jq '.objects[].fields|{"hostname": .name,"hw-address": .macaddress,"ip-address": .ipaddress_id_friendlyname}'; }
rest|grep -A1 -B3 10.1.     |sed '$!s/}/},/'>$RES/10.1.pc.json
rest|grep -A1 -B3 192.168.1.|sed '$!s/}/},/'>$RES/192.pc.json
echo '{ "command": "config-reload" }'|nc local:/run/kea/kea-dhcp4-ctrl.sock

And snippet of /etc/kea/kea.conf:

{
"Dhcp4": {
    "subnet4": [
        {
            "subnet": "10.1.0.0/16",
            "reservations": [
                <?include "/etc/kea/reservations/10.1.pc.json"?>
            ]
        },
        {
            "subnet": "192.168.1.0/24",
            "option-data": [
                {
                    "name": "routers",
                    "data": "192.168.1.1"
                }
            ],
            "reservations": [
                <?include "/etc/kea/reservations/192.pc.json"?>,
                <?include "/etc/kea/reservations/192.print.json"?>
            ]
        }

I hope it helps. Cheers!

[Xtophe38]

Hi,

No worries for the late answer and thank you for sharing this information. For sure, that will help when I'll create the service that builds DHCP conf files.

Cheers !