Behaviour mismatch with `dig`; invalid domain for `xn--aa.com`

[all-is-to-be-dared]

Expected: doge correctly queries domain.
Got: doge raises an invalid domain error.

Version:

> doge --version
doge  command-line DNS client
v0.2.9
https://dns.lookup.dog/

Command:

> doge xn--aa.com
doge: Invalid options: Invalid domain "xn--aa.com"
> dig xn--aa.com

; <<>> DiG 9.20.15-1~deb13u1-Debian <<>> xn--aa.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21890
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;��.com.			IN	A

;; AUTHORITY SECTION:
com.			900	IN	SOA	a.gtld-servers.net. nstld.verisign-grs.com. 1765503430 1800 900 604800 900

;; Query time: 16 msec
;; SERVER: 169.254.169.254#53(169.254.169.254) (UDP)
;; WHEN: Fri Dec 12 01:37:32 UTC 2025
;; MSG SIZE  rcvd: 112

[Dj-Codeman]

This is IDNA2008 parsing with the punycode and xn-- escape. Earlier versions of dig refused that by default or threw a warning, needing a +noidnin flag added:

> dig -v
DiG 9.18.44

> dig xn--aa.com
dig: 'xn--aa.com' is not a legal IDNA2008 name (domain label has character forbidden in non-transitional mode (TR46)), use +noidnin

> dig +noidnin xn--aa.com

; <<>> DiG 9.18.44 <<>> +noidnin xn--aa.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58781
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
dig: 'xn--aa.com.' is not a legal IDNA2008 name (string contains a disallowed character), use +noidnout

Personally I'm a bigger fan of that implementation because unless you're intentionally trying to test resolver responses or something deep in dns itself you should never be passing domains like this. This did make me realize that there is no +noindin option in doge tho, its definitly something to look into