.test TLD not resolving

Please follow the below template, it will help us to help you!

Expected Behaviour:

Requesting the IP for craft.test should have the request passed to the upstream resolve and an answer returned.

Actual Behaviour:

I'm using Bind as an upstream resolver for a bunch of internal domains, two relevant ones .krynn.int and .test.

Everything is working fine if I request an IP for blah.krynn.int, Pi-hole passes up the request and I get an IP.

If I request something on .test, say craft.test I don't get an answer. From the log file I see:

Nov 30 12:02:05 dnsmasq[5069]: query[A] craft.test from 192.168.0.7
Nov 30 12:02:05 dnsmasq[5069]: config craft.test is NXDOMAIN

The subdomain does exist on the upstream DNS:

# dig @localhost -p 5353 craft.test

; <<>> DiG 9.16.33-Debian <<>> @localhost -p 5353 craft.test
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21345
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 04ce162fae7e844701000000638747887161ae668a912df0 (good)
;; QUESTION SECTION:
;craft.test.                    IN      A

;; ANSWER SECTION:
craft.test.             300     IN      A       192.168.0.52

;; Query time: 0 msec
;; SERVER: ::1#5353(::1)
;; WHEN: Wed Nov 30 12:07:36 GMT 2022
;; MSG SIZE  rcvd: 83

I have Never forward non-FQDN A and AAAA queries turned off and have stopped and restarted the service.

I've checked it is in the config file:

BLOCKING_ENABLED=true
CONDITIONAL_FORWARDING=false
DNSMASQ_LISTENING=single
DNS_FQDN_REQUIRED=false
DNS_BOGUS_PRIV=true
DNSSEC=false
REV_SERVER=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.0.8/24
IPV6_ADDRESS=
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
CACHE_SIZE=10000
PIHOLE_DNS_1=192.168.0.8#5353

This was working before I upgraded to the latest version:

Pi-hole v5.14.2 FTL v5.19.2 Web Interface v5.17

What has changed and what do I need to change back to get it working again?

Debug Token:

I'll upload data from the debug log if required.

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

In reading thorough the debug info before posting it I've found the problem:

/etc/dnsmasq.d/06-rfc6761.conf

# RFC 6761: Caching DNS servers SHOULD recognize
#     test, localhost, invalid
# names as special and SHOULD NOT attempt to look up NS records for them, or
# otherwise query authoritative DNS servers in an attempt to resolve these
# names.
server=/test/

This must be new as I've been using this domain for years and it only broke on this last update. If I comment this line out and restart the service everything resolves fine.

Maybe I shouldn't be using .test. but I moved to it from .dev when Google acquired dev and broke it for home use.

No... This was implemented 2021.

1 Like

Shows how long since I last updated then doesn't it.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.