Indeed, I do not see this behavior any longer.
``` $ dig -x 127.0.0.1
; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> -x 127.0.0.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12678 ;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;1.0.0.127.in-addr.arpa. IN PTR
;; ANSWER SECTION: 1.0.0.127.in-addr.arpa. 0 IN PTR localhost. 1.0.0.127.in-addr.arpa. 0 IN PTR kubernetes.docker.internal.
;; Query time: 3 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) ;; WHEN: Fri Jun 23 11:29:26 CDT 2023 ;; MSG SIZE rcvd: 114
$ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 ```
Indeed, I do not see this behavior any longer.
```
$ dig -x 127.0.0.1
; <<>> DiG 9.18.12- 0ubuntu0. 22.04.2- Ubuntu <<>> -x 127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12678
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: 127.in- addr.arpa. IN PTR
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;1.0.0.
;; ANSWER SECTION: in-addr. arpa. 0 IN PTR localhost. in-addr. arpa. 0 IN PTR kubernetes. docker. internal.
1.0.0.127.
1.0.0.127.
;; Query time: 3 msec 53#53(127. 0.0.53) (UDP)
;; SERVER: 127.0.0.
;; WHEN: Fri Jun 23 11:29:26 CDT 2023
;; MSG SIZE rcvd: 114
$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
```