Question about 'bad referral'

[yylee at dacom.net]

From: 이영윤 4496 at DACOM on 2000-05-10 11:46 AM

To:   bind-users at isc.org
cc:
Subject:  Question about 'bad referral'


  I managed two DNS servers.
  One is caching-only server and the other works as forwarder of it.
  But, I saw the strange thing.

  When the caching-only server sent queries(www.???.com -> ex.www.abc.com),
  sometimes forwarder’s logging file was written like below.

     bad referral (. !< ???.COM)

  And, forwarder sent the message like below to caching-only server.

     ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47104
     ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
     ;;   www.???.com, type = A, class = IN
     www.???.com.         23h53m20s IN A      123.456.789.0
     .              0S IN NS   .
     .              0S IN A         0.0.0.0

  If the caching-only server sent another query(www.????.com) shortly after
  receiving this answer,
  the logging file of caching-only server was written like below and
  the caching-only server couldn’t resolve this query.

     ns_forw: query(www.????.com) Bogus (0.0.0.0) A RR (:0.0.0.0)
     sysquery: query() Bogus (0.0.0.0) A RR (:0.0.0.0)
     sysquery: no addrs found for root NS ()

  What’s means of “bad referral”?
  Even if TTL is 0, why affect next query?
  Thanks in advance for your help.