b10-resolver (as forwarder) exit with SEGV

[jreed]

Not sure what caused this b10-resolver to exit with SEGV.

I am confused why question generates different upstream questions and one question results in multiple responses. Is this an error too?

Here is the closest lines in verbose output:

[b10-resolver] Got a DNS message
[b10-resolver] received a message:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21919
;; flags: rd ; QUESTION: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;external.ak.fbcdn.net. IN A

[b10-resolver] Processing normal query
[b10-resolver] Try out cache first (started by incoming event)
[b10-resolver] Message not found in cache, starting recursive query
[b10-resolver] doLookup: try cache
[b10-resolver] Sending upstream query (external.ak.fbcdn.net. IN A
) to 127.0.0.1
[b10-resolver] Timeout, resending query
[b10-resolver] Sending upstream query (profile.ak.fbcdn.net. IN A
) to 127.0.0.1
[b10-resolver] Timeout, resending query
[b10-resolver] Sending upstream query (photos-e.ak.fbcdn.net. IN A
) to 127.0.0.1

[b10-resolver] Timeout, resending query
[b10-resolver] Sending upstream query (external.ak.fbcdn.net. IN A
) to 127.0.0.1
[b10-resolver] sending a response (442bytes): 
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3781
;; flags: qr rd ra ; QUESTION: 1, ANSWER: 11, AUTHORITY: 9, ADDITIONAL: 0

;; QUESTION SECTION:
;photos-e.ak.fbcdn.net. IN A

;; ANSWER SECTION:
photos-e.ak.fbcdn.net. 895 IN CNAME photos-a.ak.facebook.com.edgesuite.net.
photos-a.ak.facebook.com.edgesuite.net. 4798 IN CNAME a995.mm1.akamai.net.
a995.mm1.akamai.net. 20 IN A 69.31.72.194
a995.mm1.akamai.net. 20 IN A 69.31.72.139
a995.mm1.akamai.net. 20 IN A 69.31.72.145
a995.mm1.akamai.net. 20 IN A 69.31.72.147
a995.mm1.akamai.net. 20 IN A 69.31.72.169
a995.mm1.akamai.net. 20 IN A 69.31.72.176
a995.mm1.akamai.net. 20 IN A 69.31.72.178
a995.mm1.akamai.net. 20 IN A 69.31.72.184
a995.mm1.akamai.net. 20 IN A 69.31.72.193


;; AUTHORITY SECTION:
mm1.akamai.net. 1798 IN NS n7mm1.akamai.net.
mm1.akamai.net. 1798 IN NS n4mm1.akamai.net.
mm1.akamai.net. 1798 IN NS n3mm1.akamai.net.
mm1.akamai.net. 1798 IN NS n2mm1.akamai.net.
mm1.akamai.net. 1798 IN NS n5mm1.akamai.net.
mm1.akamai.net. 1798 IN NS n0mm1.akamai.net.
mm1.akamai.net. 1798 IN NS n6mm1.akamai.net.
mm1.akamai.net. 1798 IN NS a0mm1.akamai.net.
mm1.akamai.net. 1798 IN NS n1mm1.akamai.net.

[b10-resolver] Timeout, resending query
[b10-resolver] Sending upstream query (profile.ak.fbcdn.net. IN A
) to 127.0.0.1
[b10-resolver] sending a response (308bytes): 
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21919
;; flags: qr rd ra ; QUESTION: 1, ANSWER: 4, AUTHORITY: 9, ADDITIONAL: 0

;; QUESTION SECTION:
;external.ak.fbcdn.net. IN A

;; ANSWER SECTION:
external.ak.fbcdn.net. 2472 IN CNAME external.ak.fbcdn.net.edgesuite.net.
external.ak.fbcdn.net.edgesuite.net. 4798 IN CNAME a1920.g.akamai.net.
a1920.g.akamai.net. 20 IN A 63.80.138.48
a1920.g.akamai.net. 20 IN A 63.80.138.67

;; AUTHORITY SECTION:
g.akamai.net. 1799 IN NS n4g.akamai.net.
g.akamai.net. 1799 IN NS n7g.akamai.net.
g.akamai.net. 1799 IN NS n6g.akamai.net.
g.akamai.net. 1799 IN NS a0g.akamai.net.
g.akamai.net. 1799 IN NS n5g.akamai.net.
g.akamai.net. 1799 IN NS n3g.akamai.net.
g.akamai.net. 1799 IN NS n0g.akamai.net.
g.akamai.net. 1799 IN NS n1g.akamai.net.
g.akamai.net. 1799 IN NS n2g.akamai.net.

[b10-resolver] sending a response (38bytes): 
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 24087
;; flags: qr rd ra ; QUESTION: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;profile.ak.fbcdn.net. IN A

[bind10] Process b10-resolver (PID 16152) terminated, exit status = 139

[jreed]

Note this is a forwarder. It should not be doing upstream queries asking for the addresses for the nameservers.

[jreed]

Maybe this issue is already fixed. I don't know. I now see the verbose out put changed to also say "Asked to resolve:".

[tomek]

DNS and BIND10 framework is outside of scope for Kea project.
The corresponding code has been removed from Kea git repository.
If you want to follow up on DNS or former BIND10 issues, see
​​http://bundy-dns.de project.

Closing ticket.