BiPac 880AXL R2 persistent PTR rercord
Posted: Wed Apr 28, 2021 4:40 pm
I have inadvertently booted a Raspberry Pi 4 (RPI4) using the same hostname as another RPI4 on my home network. Once I've resolved this and rebooted both RPI4s the BiPac router still reports the PTR for the same (incorrect) hostname.
I see
pi@raspberrypi:~ $ dig -x 192.168.1.121
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> -x 192.168.1.121
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49176
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: f0da57d7fee81c5c (echoed)
;; QUESTION SECTION:
;121.1.168.192.in-addr.arpa. IN PTR
;; ADDITIONAL SECTION:
121.1.168.192.in-addr.arpa. 308231 IN PTR PiTv.home.gateway.
;; Query time: 1 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Wed Apr 28 15:37:02 BST 2021
;; MSG SIZE rcvd: 98
pi@raspberrypi:~ $ dig -x 192.168.1.100
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> -x 192.168.1.100
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43025
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 4bf134e17831d5c0 (echoed)
;; QUESTION SECTION:
;100.1.168.192.in-addr.arpa. IN PTR
;; ADDITIONAL SECTION:
100.1.168.192.in-addr.arpa. 308243 IN PTR PiTv.home.gateway.
;; Query time: 0 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Wed Apr 28 15:37:15 BST 2021
;; MSG SIZE rcvd: 98
pi@raspberrypi:~ $ dig PiTv.home.gateway
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> PiTv.home.gateway
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6786
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 171aa59ffac2bb87 (echoed)
;; QUESTION SECTION:
;PiTv.home.gateway. IN A
;; ADDITIONAL SECTION:
PiTv.home.gateway. 311791 IN A 192.168.1.121
;; Query time: 1 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Wed Apr 28 16:36:21 BST 2021
;; MSG SIZE rcvd: 74
The IP address 192.168.1.121 is no longer leased to any device, yet the BiPac keeps resolving this to the PiTv host.
Is there any way to force the BiPac to drop this PTR record? Or is it the A record? Either way, the incorrect IP address is being resolved to the correct hostname.
I see
pi@raspberrypi:~ $ dig -x 192.168.1.121
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> -x 192.168.1.121
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49176
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: f0da57d7fee81c5c (echoed)
;; QUESTION SECTION:
;121.1.168.192.in-addr.arpa. IN PTR
;; ADDITIONAL SECTION:
121.1.168.192.in-addr.arpa. 308231 IN PTR PiTv.home.gateway.
;; Query time: 1 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Wed Apr 28 15:37:02 BST 2021
;; MSG SIZE rcvd: 98
pi@raspberrypi:~ $ dig -x 192.168.1.100
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> -x 192.168.1.100
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43025
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 4bf134e17831d5c0 (echoed)
;; QUESTION SECTION:
;100.1.168.192.in-addr.arpa. IN PTR
;; ADDITIONAL SECTION:
100.1.168.192.in-addr.arpa. 308243 IN PTR PiTv.home.gateway.
;; Query time: 0 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Wed Apr 28 15:37:15 BST 2021
;; MSG SIZE rcvd: 98
pi@raspberrypi:~ $ dig PiTv.home.gateway
;; Warning: Message parser reports malformed message packet.
; <<>> DiG 9.11.5-P4-5.1+deb10u3-Raspbian <<>> PiTv.home.gateway
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6786
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 171aa59ffac2bb87 (echoed)
;; QUESTION SECTION:
;PiTv.home.gateway. IN A
;; ADDITIONAL SECTION:
PiTv.home.gateway. 311791 IN A 192.168.1.121
;; Query time: 1 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Wed Apr 28 16:36:21 BST 2021
;; MSG SIZE rcvd: 74
The IP address 192.168.1.121 is no longer leased to any device, yet the BiPac keeps resolving this to the PiTv host.
Is there any way to force the BiPac to drop this PTR record? Or is it the A record? Either way, the incorrect IP address is being resolved to the correct hostname.