Avatar of Mark
Mark
 asked on

Having issues with old data, DNS/DHCP

I'm having a few issues with DNS/DHCP, I'll ask about these one at a time.

bind 9.9.7-P1, dhcpd 4.2.5-P1, Slackware 64, 14.1

First, old leases seem to hang around forever in /var/state/dhcp/dhcpd.leases, example below. Those listed are from back in March. None of the computers in the lease file are currently connected. Why are they hanging around?

Should static IPs be in there? If so, something is not working.

/var/state/dhcp/dhcpd.leases
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.2.5-P1

lease 192.168.0.101 {
  starts 6 2015/03/07 11:46:52;
  ends 0 2015/03/08 11:46:52;
  tstp 0 2015/03/08 11:46:52;
  cltt 6 2015/03/07 11:46:52;
  binding state free;
  hardware ethernet 00:16:17:46:70:69;
  uid "\001\000\026\027Fpi";
}
lease 192.168.0.104 {
  starts 2 2015/03/17 17:01:10;
  ends 3 2015/03/18 17:01:10;
  tstp 3 2015/03/18 17:01:10;
  cltt 2 2015/03/17 17:01:10;
  binding state free;
  hardware ethernet c8:9c:dc:6e:24:e8;
  uid "\001\310\234\334n$\350";
}

Open in new window


My dhcpd.conf file:

authoritative;

ddns-updates on;
update-static-leases on;
allow unknown-clients;  # default, deprecated (man dhcpd.conf)
ignore client-updates;  # see https://www.centos.org/forums/viewtopic.php?t=29256, man dhcpd.conf: ignore client-updates
ddns-update-style interim;
default-lease-time 86400;

log-facility local7;

zone hprs.local. { primary 192.168.0.2; }
zone 0.168.192.in-addr.arpa. { primary 192.168.0.2; }

subnet 192.168.0.0 netmask 255.255.255.0 {
    option routers 192.168.0.2;
    range 192.168.0.100 192.168.0.254;
    option domain-name-servers 192.168.0.2;
    option domain-name "hprs.local";
    ddns-domainname = "hprs.local.";
    ddns-rev-domainname = "in-addr.arpa.";
}

# Web Server (Linux)
host webserver {
    hardware ethernet 60:A4:4C:61:9C:FE;
    fixed-address 192.168.0.3;
}

# SQL Server Database Server (Server 2008)
host server {
#    hardware ethernet 40:E0:4C:39:7F:61;
    hardware ethernet 3C:1E:04:47:16:B0;
    fixed-address 192.168.0.4;
}

# Network Attached Storage (Linux)
host ohprsstorage {
    hardware ethernet F4:6D:04:60:04:38;
    fixed-address 192.168.0.5;
}

# COMMON workstation (WIN7)
host COMMON {
    hardware ethernet 2C:27:D7:2F:CF:7A;
    fixed-address 192.168.0.58;
}

host ricoh {
    hardware ethernet 00:26:73:55:63:AB;
    fixed-address 192.168.0.20;
}

# Postage meter
host postage {
    hardware ethernet 00:10:60:B6:72:D4;
    fixed-address 192.168.0.21;
}

Open in new window

Linux NetworkingDHCP

Avatar of undefined
Last Comment
Daniel McAllister

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Daniel McAllister

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Mark

ASKER
So ... "old" leases never get purged from that file? It just grows forever?

Dan: that script worked well.

IPs statically assigned are not in the lease file, eh? Is that correct? None of my dozen-ish static assignments show as active leases.
Daniel McAllister

Yes, again it is as much a LOG file as anything.

Dan
IT4SOHO
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck