It's really more like bad-answer than no-answer.

This commit is contained in:
Tony Garnock-Jones 2012-02-18 11:16:17 -05:00
parent 776e4ad58b
commit 1d3cb6f094
1 changed files with 4 additions and 4 deletions

View File

@ -115,7 +115,7 @@
'()
'()))
;; filter-dns-reply : DNSMessage DomainName -> (or Maybe<CompleteAnswer> 'no-answer)
;; filter-dns-reply : DNSMessage DomainName -> (or Maybe<CompleteAnswer> 'bad-answer)
;;
;; Filters RRs from the answer, authorities, and additional sections
;; of the passed-in `message`, returning the set of RRs surviving the
@ -123,7 +123,7 @@
;; bailiwick of the given `zone-origin`. All of this only happens if
;; the passed-in message's `dns-message-response-code` is `'no-error`:
;; if it's `'name-error`, then `#f` is returned, and if it's any other
;; code, `'no-answer` is returned.
;; code, `'bad-answer` is returned.
(define (filter-dns-reply message zone-origin)
(case (dns-message-response-code message)
[(no-error)
@ -137,7 +137,7 @@
(begin (write `(Abnormal response-code ,(dns-message-response-code message) received
in response to questions ,(dns-message-questions message)))
(newline))
'no-answer]))
'bad-answer]))
;; IPv4 -> String
(define (ip->host-name ip-address)
@ -205,7 +205,7 @@
(unsubscribe rpc-id))])))]))
(define (on-answer w ans)
(if (eq? ans 'no-answer) ;; can come from filter-dns-reply
(if (eq? ans 'bad-answer) ;; can come from filter-dns-reply
(try-next-server w)
(transition w
(send-message (network-reply (network-request-unique-id (network-query-state-request w))