<div dir="ltr">Where's your dhcpd.conf declaration for 10.168.192.in-addr.arpa?<div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 24, 2020 at 5:23 PM Dan Egli <dan@newideatest.site> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Alright. I did a test, and it's still not even trying to create
the reverse mapping. I don't know why. I created a machine called
terra. It asked dhcpd for a least. It got a lease. But that least
never made it to named's in-addr.arpa zone, even though named is
running too. I'm at a loss as to what's up and why it won't try to
create the reverse DNS pointer. the DNS. Here's the setup:</p>
<p>terra: Booting from a Gentoo Minimal CD, running dhcpcd -h terra
so that the hostname gets passed to dhcpd</p>
<p>pluto: dhcpd running. Receives a lease request, offers a new
least, receive the ack, writes the forward mapping, ends. Does not
write the reverse mapping. Here's the log segment:</p>
<p>Dec 24 15:02:22 pluto dhcpd[2439]: DHCPDISCOVER from
08:00:27:03:d3:23 via enp0s8<br>
Dec 24 15:02:23 pluto dhcpd[2439]: DHCPOFFER on 192.168.10.128 to
08:00:27:03:d3:23 (terra) via enp0s8<br>
Dec 24 15:02:23 pluto dhcpd[2439]: DHCPREQUEST for 192.168.10.128
(192.168.10.1) from 08:00:27:03:d3:23 (terra) via enp0s8<br>
Dec 24 15:02:23 pluto dhcpd[2439]: DHCPACK on 192.168.10.128 to
08:00:27:03:d3:23 (terra) via enp0s8<br>
Dec 24 15:02:23 pluto dhcpd[2439]: Added new forward map from
<a href="http://terra.eglifamily.name" target="_blank">terra.eglifamily.name</a> to 192.168.10.128<br>
</p>
<p><br>
</p>
<p>As you can see, dig works for terra, not for it's IP:</p>
<p>pluto /etc/systemd # dig a +short <a href="http://terra.eglifamily.name" target="_blank">terra.eglifamily.name</a><br>
192.168.10.128<br>
pluto /etc/systemd # dig a -x +short 192.168.10.128<br>
pluto /etc/systemd # dig ptr -x 192.168.10.128<br>
; <<>> DiG 9.16.6 <<>> ptr -x
192.168.10.128<br>
;; global options: +cmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id:
14327<br>
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1,
ADDITIONAL: 1<br>
<br>
;; OPT PSEUDOSECTION:<br>
; EDNS: version: 0, flags:; udp: 4096<br>
; COOKIE: 0de11839ad25b1b5010000005fe51320c8672852930cb66c (good)<br>
;; QUESTION SECTION:<br>
;128.10.168.192.in-addr.arpa. IN PTR<br>
<br>
;; AUTHORITY SECTION:<br>
10.168.192.in-addr.arpa. 60 IN SOA
<a href="http://pluto.eglifamily.name" target="_blank">pluto.eglifamily.name</a>. <a href="http://dan.eglifamily.name" target="_blank">dan.eglifamily.name</a>. 2 1800 300 86400 60<br>
<br>
;; Query time: 0 msec<br>
;; SERVER: 127.0.0.1#53(127.0.0.1)<br>
;; WHEN: Thu Dec 24 15:16:00 MST 2020<br>
;; MSG SIZE rcvd: 145<br>
<br>
pluto /etc/systemd # dig +short ptr -x 192.168.10.128<br>
pluto /etc/systemd #<br>
<br>
So, pluto is obviously recognized as the SOA for 192.168.10.x,
which is good. Why then is dhcpd only sending a forward mapping?<br>
</p>
<p>FWIW, although they haven't changed, I'll repost the zone files
and the config files.</p>
<p>eglifamily.zone:</p>
<p>$ORIGIN .<br>
$TTL 21600 ; 6 hours<br>
<a href="http://eglifamily.name" target="_blank">eglifamily.name</a> IN SOA <a href="http://pluto.eglifamily.name" target="_blank">pluto.eglifamily.name</a>.
<a href="http://dan.eglifamily.name" target="_blank">dan.eglifamily.name</a>. (<br>
4 ; serial<br>
1800 ; refresh (30 minutes)<br>
300 ; retry (5 minutes)<br>
86400 ; expire (1 day)<br>
60 ; minimum (1 minute)<br>
)<br>
NS <a href="http://pluto.eglifamily.name" target="_blank">pluto.eglifamily.name</a>.<br>
MX 1 <a href="http://jupiter.eglifamily.name" target="_blank">jupiter.eglifamily.name</a>.<br>
charon A 192.158.10.1<br>
jupiter A 192.168.10.3<br>
pluto A 192.168.10.2<br>
$TTL 1800 ; 30 minutes<br>
terra A 192.168.10.128<br>
TXT
"311fd3292f4dc507ed06f247665a4ac9ab"<br>
</p>
<p>That's after terra gets registered, obviously. But at the same
time, here's the reverse zone.</p>
<p>10.168.192.arpa.zone:<br>
$TTL 10m<br>
@ IN SOA <a href="http://pluto.eglifamily.name" target="_blank">pluto.eglifamily.name</a>. <a href="http://dan.eglifamily.name" target="_blank">dan.eglifamily.name</a>. (<br>
2 ; serial<br>
30m ; refresh<br>
5m ; retry<br>
1d ; expire<br>
1m ; negative response
cache<br>
)<br>
NS <a href="http://pluto.eglifamily.name" target="_blank">pluto.eglifamily.name</a>.<br>
1 PTR <a href="http://charon.eglifamily.name" target="_blank">charon.eglifamily.name</a>.<br>
2 PTR <a href="http://pluto.eglifamily.name" target="_blank">pluto.eglifamily.name</a>.<br>
3 PTR <a href="http://jupiter.eglifamily.name" target="_blank">jupiter.eglifamily.name</a>.<br>
</p>
<p>Notice no PTR to terra. As to config files, here's dhcpd:</p>
<p>default-lease-time 3600;<br>
max-lease-time 43200;<br>
<br>
ddns-update-style interim;<br>
<br>
authoritative;<br>
log-facility local1;<br>
<br>
<br>
allow booting;<br>
<br>
subnet 10.0.0.0 netmask 255.0.0.0 {<br>
# no services at all! That's the llnk from the ISP. Don't touch
it!<br>
}<br>
<br>
<br>
subnet 192.168.10.0 netmask 255.255.255.0 {<br>
interface enp0s8;<br>
range 192.168.10.128 192.168.10.254;<br>
if exists user-class and option user-class = "iPXE" {<br>
filename "pxelinux.efi";<br>
} else {<br>
filename "pxelinux.0";<br>
}<br>
next-server 192.168.10.3;<br>
option domain-name-servers 192.168.10.2;<br>
option domain-name "<a href="http://eglifamily.name" target="_blank">eglifamily.name</a>";<br>
option routers 192.168.10.1;<br>
<br>
}<br>
<br>
host fixed-1 {<br>
hardware ethernet 08:00:27:D5:AA:3C;<br>
fixed-address 192.168.10.64;<br>
option host-name "fixed-1";<br>
ddns-hostname "<a href="http://fixed-1.eglifamily.name" target="_blank">fixed-1.eglifamily.name</a>";<br>
}<br>
</p>
<p><br>
</p>
<p>And here's named.conf:</p>
<p><br>
</p>
<div>On 12/22/2020 7:48 AM,
/etc/bind/named.conf<br>
acl "xfer" {<br>
none;<br>
};<br>
acl "trusted" {<br>
<a href="http://10.0.2.15/32" target="_blank">10.0.2.15/32</a>;<br>
<a href="http://192.168.10.0/24" target="_blank">192.168.10.0/24</a>;<br>
<a href="http://127.0.0.0/8" target="_blank">127.0.0.0/8</a>;<br>
::1/128;<br>
# eventualy add valid IPv6 addresses here.<br>
};<br>
<br>
acl "myself" {<br>
<a href="http://127.0.0.0/24" target="_blank">127.0.0.0/24</a>;<br>
::1/128;<br>
<a href="http://192.168.10.2/32" target="_blank">192.168.10.2/32</a>;<br>
<a href="http://10.0.2.15/32" target="_blank">10.0.2.15/32</a>;<br>
};<br>
<br>
options {<br>
directory "/var/bind";<br>
pid-file "/run/named/named.pid";<br>
tkey-gssapi-keytab "/var/lib/samba/bind-dns/dns.keytab";<br>
minimal-responses yes;<br>
<br>
<br>
listen-on-v6 { none; }; // for now<br>
listen-on { 192.168.10.2; 127.0.0.1; };<br>
<br>
allow-query {<br>
trusted;<br>
};<br>
<br>
allow-query-cache {<br>
trusted;<br>
};<br>
<br>
allow-recursion {<br>
trusted;<br>
};<br>
<br>
allow-transfer {<br>
none;<br>
};<br>
<br>
allow-update {<br>
myself;<br>
};<br>
<br>
dnssec-validation auto;<br>
};<br>
<br>
<br>
logging {<br>
channel default_log {<br>
file "/var/log/named/named.log" versions 5 size
50M;<br>
print-time yes;<br>
print-severity yes;<br>
print-category yes;<br>
};<br>
<br>
category default { default_log; };<br>
category general { default_log; };<br>
};<br>
<br>
<br>
include "/etc/bind/rndc.key";<br>
controls {<br>
inet 127.0.0.1 port 953 allow { <a href="http://127.0.0.1/32" target="_blank">127.0.0.1/32</a>; ::1/128; }
keys { "rndc-key"; };<br>
};<br>
<br>
zone "localhost" IN {<br>
type master;<br>
file "pri/localhost.zone";<br>
notify no;<br>
};<br>
<br>
zone "<a href="http://eglifamily.name" target="_blank">eglifamily.name</a>" {<br>
type master;<br>
file "pri/eglifamily.zone";<br>
notify yes;<br>
};<br>
<br>
<br>
zone "10.168.192.in-addr.arpa" {<br>
type master;<br>
file "pri/10.168.192.arpa.zone";<br>
notify yes;<br>
};<br>
<br>
include "/var/lib/samba/bind-dns/named.conf";<br>
</div>
<div><br>
</div>
<div>So, what is wrong?</div>
<div><br>
</div>
<div><br>
</div>
<pre>--
</pre>
<pre cols="72">Dan Egli
From my Test Server</pre>
</div>
_______________________________________________<br>
ISC funds the development of this software with paid support subscriptions. Contact us at <a href="https://www.isc.org/contact/" rel="noreferrer" target="_blank">https://www.isc.org/contact/</a> for more information.<br>
<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" rel="noreferrer" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote></div>