|George Langford via plug on 25 Nov 2021 07:28:26 -0800|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|Re: [PLUG] DNS, fsearch, systemd|
jeffv has brought up recently.I've just found a class of mis-configured in-addr.arpa entries that ought to disrupt
DNS lookups. Here's a ferinstance: 184.108.40.206/25.There's a misconfiguration in the in-addr.arpa index address for more than fifty of these
IPv4 addresses: dig -x 220.127.116.11 ==> ;; ANSWER SECTION:18.104.22.168.in-addr.arpa. 1200 IN CNAME 156.128-22.214.171.124.in-addr.arpa. 156.128-126.96.36.199.in-addr.arpa. 7199 IN PTR server1.jobinterview.biz.
That misconfiguration ought to interfere with the resolution of server1.jobinterview.biz, but it doesn't.
Is that because I've looked up those addresses too many times ?The miscofiguration appears to stem from the original setup/registration of the server, as 128/25 is the correct CIDR block of the affected addresses. However, the injected 128-25 in 156.128-188.8.131.52.in-addr.arpa is in the wrong position of the reversed
order of IPv4 octets, as though the misconfiguration is deliberate. ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug