Fraîche Flow

Linux · Infrastructure · Networking · Virtualisation

docs/DHCP with Kea
59 lines1.81 KB

DHCP with Kea

MILOUD NECILI

Fraîche Flow · IT Systems Integration

Project objective

Distribute network settings centrally to lab clients and maintain consistency between DHCP, DNS and static server addresses.

My implementation

  • Worked on the Kea DHCP tasks on ff-core-01.
  • Treated the subnet, address pool, gateway and DNS options as a coherent configuration.
  • Checked the dynamic address of ff-mgmt-01 during the project.
  • Identified a mismatch between the DHCP address and DNS record and accounted for it in the documentation.

Technical context

Server role ff-core-01
Subnet 192.168.10.0/24
Assigned exercise pool 192.168.10.100 to 192.168.10.150
Gateway / DNS 192.168.10.1 / 192.168.10.11

Result

The project lead reported the DHCP address 192.168.10.100 earlier in the project. A complete lease export is not part of the available evidence.

Verification and operational evidence

ip -br a
ip route
cat /etc/resolv.conf
getent hosts ff-mgmt-01.fraicheflow.test

Kea DHCP service, configuration validation and DHCP port on ff-core-01

Practical troubleshooting

A DNS record temporarily pointed to .50 while the client used .100. The mismatch was identified as a possible cause of access failures.

Security and technical context

Do not adopt the exercise pool as the current target configuration without checking: .100 was also used for a Windows storage host. Static addresses and the DHCP range must not conflict.

Transferable skills

DHCP options, client configuration, address management and DNS/DHCP consistency.

Project status

Completed according to confirmation from the project lead.