If I run the example included in dig help @dns.toys, I get the following:
➜ dig 99USD-INR.fx @dns.toys
; <<>> DiG 9.16.44 <<>> 99USD-INR.fx @dns.toys
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19665
;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;99USD-INR.fx. IN A
;; ANSWER SECTION:
99USD-INR. 3600 IN TXT "99.00 USD = 8172.15 INR" "2023-05-28"
;; Query time: 64 msec
;; SERVER: 204.48.19.68#53(204.48.19.68)
;; WHEN: Mon Jan 15 05:19:24 PST 2024
;; MSG SIZE rcvd: 86
There is an old (closed) issue that suggests adjusting the config.toml to avoid this, but this behavior seems unrelated -- the data is from over half a year ago, which is well above the default refresh rate of 6 hours.
If I run the example included in
dig help @dns.toys
, I get the following:There is an old (closed) issue that suggests adjusting the
config.toml
to avoid this, but this behavior seems unrelated -- the data is from over half a year ago, which is well above the default refresh rate of 6 hours.