[SOLVED (kind of)] SERVFAIL from kresd when resolving one particular domain (TurrisOS v6.3.3 on Omnia)

Hi guys,

I’ve got issues with kresd - it refuses to resolve retail.mobile.lbi.santander.uk.

I tried to query 9.9.9.9 (and few others that I use for forwarding from my kresd) directly and it works fine. So I’m pretty sure there’s nothing wrong with the domain, the remote resolvers, nor my ISP:

root@turris:/etc# host -t A -vvv retail.mobile.lbi.santander.uk
Trying "retail.mobile.lbi.santander.uk"
root@turris:/etc# host -t A -vvv retail.mobile.lbi.santander.uk 9.9.9.9
Trying "retail.mobile.lbi.santander.uk"
Using domain server:
Name: 9.9.9.9
Address: 9.9.9.9#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2780
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;retail.mobile.lbi.santander.uk.        IN      A

;; ANSWER SECTION:
retail.mobile.lbi.santander.uk. 600 IN  A       193.127.211.80

Received 64 bytes from 9.9.9.9#53 in 220 ms

When I query localhost, I’m getting SERVFAIL:

root@turris:/etc# host -t A -vvv retail.mobile.lbi.santander.uk localhost
Trying "retail.mobile.lbi.santander.uk"
Using domain server:
Name: localhost
Address: 127.0.0.1#53
Aliases:

Host retail.mobile.lbi.santander.uk not found: 2(SERVFAIL)
Received 48 bytes from 127.0.0.1#53 in 0 ms

Btw, that “localhost” command works fine for other domains, so yes, kresd is running, is reachable, is able to resolve most domains, but it has issues with the one. I’ve been using the same config for few years already and this domain is really the only one that doesn’t work for me. Here’s a working example:

root@turris:/etc# host -t A -vvv turris.cz localhost
Trying "turris.cz"
Using domain server:
Name: localhost
Address: ::1#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33096
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;turris.cz.                     IN      A

;; ANSWER SECTION:
turris.cz.              1800    IN      A       217.31.192.69

Received 43 bytes from ::1#53 in 280 ms

I have no idea how to debug this. I wasn’t able to find out how to get any debug logging working.

:man_shrugging:

Any suggestions?

I found out it is caused by knotd itself (when I tried it in another environment).

I’ve raised the issue in the knotd Gitlab. In the meantime, I’m switching to another DNS on my Turris. :-1:

For reference, the discussion’s moved to