I have set up a private AWS Route 53 hosted zone.
If I run nslookup on the newly added entry, I receive an error:
$nslookup search.syndey.recap
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find search.syndey.recap: NXDOMAIN
However, if I request the same thing from dig, I get a (correct) result
$ dig search.sydney.recap
; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> search.sydney.recap
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56763
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;search.sydney.recap. IN A
;; ANSWER SECTION:
search.sydney.recap. 300 IN CNAME i-03cd02d0d3695af77.ap-southeast-2.compute.internal.
i-03cd02d0d3695af77.ap-southeast-2.compute.internal. 60 IN A 172.32.38.206
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Nov 23 09:15:48 UTC 2023
;; MSG SIZE rcvd: 129
They both appear to me to be using the same source (127.0.0.53), why might they be giving different results? What should I look for to troubleshoot this?