Re: [*SP4M*] DHCPd only updating the forward zone

[Dan Egli]

On Thursday, December 24, 2020 09:20 PM MST, Rick Dicaire <kritek at gmail.com> wrote: 
> 
> Do you see anything in syslog from dhcpd or named?

Nothing that makes any sense. I finally finished terra, so it's not using dhcpcd anymore, but systemd. Still, systemd is sending the hostname, as you can see from the log snip below:
==> /var/log/dhcpd.log <==
Dec 26 05:54:15 pluto dhcpd[952]: Copyright 2004-2020 Internet Systems Consortium.
Dec 26 05:54:15 pluto dhcpd[952]: All rights reserved.
Dec 26 05:54:15 pluto dhcpd[952]: For info, please visit https://www.isc.org/software/dhcp/
Dec 26 05:54:15 pluto dhcpd[952]: Wrote 0 deleted host decls to leases file.
Dec 26 05:54:15 pluto dhcpd[952]: Wrote 0 new dynamic host decls to leases file.
Dec 26 05:54:15 pluto dhcpd[952]: Wrote 0 leases to leases file.
Dec 26 05:54:15 pluto dhcpd[952]: Listening on LPF/enp0s8/08:00:27:0c:5c:4a/192.168.10.0/24
Dec 26 05:54:15 pluto dhcpd[952]: Sending on   LPF/enp0s8/08:00:27:0c:5c:4a/192.168.10.0/24
Dec 26 05:54:15 pluto dhcpd[952]: Sending on   Socket/fallback/fallback-net
Dec 26 05:54:15 pluto dhcpd[952]: Server starting service.
Dec 26 05:55:49 pluto dhcpd[952]: DHCPDISCOVER from 08:00:27:02:b2:6b (terra) via enp0s8
Dec 26 05:55:49 pluto dhcpd[952]: DHCPOFFER on 192.168.10.128 to 08:00:27:02:b2:6b (terra) via enp0s8
Dec 26 05:55:49 pluto dhcpd[952]: DHCPREQUEST for 192.168.10.128 (192.168.10.1) from 08:00:27:02:b2:6b (terra) via enp0s8
Dec 26 05:55:49 pluto dhcpd[952]: DHCPACK on 192.168.10.128 to 08:00:27:02:b2:6b (terra) via enp0s8
Dec 26 05:55:49 pluto dhcpd[952]: Added new forward map from terra.eglifamily.name to 192.168.10.128

So, dhcpd added a forward map, but no reverse map. Why? Here's the zone files:

eglifamily.zone file:
$TTL 21600      ; 6 hours
@                       IN SOA  pluto.eglifamily.name. dan.eglifamily.name. (
                                2          ; serial
                                1800       ; refresh (30 minutes)
                                300        ; retry (5 minutes)
                                86400      ; expire (1 day)
                                60         ; minimum (1 minute)
                                )
                        NS      pluto.eglifamily.name.
                        MX      1 jupiter.eglifamily.name.
$ORIGIN eglifamily.name.
charon                  A       192.158.10.1
jupiter                 A       192.168.10.3
pluto                   A       192.168.10.2
$TTL 1800       ; 30 minutes
terra                   A       192.168.10.128
                        TXT     "3134bafe77ab7232c3190ea6548c12ad32"


And like I said before. I know the refresh and retry and what not are ridiculously low. Once I get this fixed I'll set them for real values. I also restarted named to ensure that it flushed the journal and wrote out the new zone info showing terra. Meanwhile, here's 10.168.192.arpa.zone:
$TTL 6h
@                               IN SOA  pluto.eglifamily.name. dan.eglifamily.nme. (
                                2          ; serial
                                30m        ; refresh
                                5m         ; retry
                                1d         ; expire
                                1m         ; negative response cache
                                )
                        NS      pluto.eglifamily.name.
1                       PTR     charon.eglifamily.name.
2                       PTR     pluto.eglifamily.name.
3                       PTR     jupiter.eglifamily.name.



So why is it not writing even the forward zone? Here's systemd's network file:
[Match]
Name=enp*

[Network]
DHCP=yes

[DHCPv4]
SendHostname=yes
UseDomain=yes

-- 
Dan Egli
>From my Test server