Closed GoogleCodeExporter closed 9 years ago
Query type 28 is for AAAA (IP6) records. The Java RI does not support
returning these types of records. I realize the config-ui allows the entry of
AAAA records; however they are not yet supported in the server. If you would
them to be supported, please log an enhancement bug.
Original comment by gm2...@cerner.com
on 1 Dec 2011 at 2:59
We have not created any AAAA records in the DNS server (these fields are empty
in the config-ui). I am not sure why we are getting this error.
Original comment by nikolai....@gmail.com
on 1 Dec 2011 at 4:21
Someone is hitting your DNS server with Type AAAA queries. Is your DNS server
exposed to a public or external network? I don't think the TRACE logs capture
the query source IP, but it's something I think should be added into the DNS
server for this type of use case.
Original comment by gm2...@cerner.com
on 2 Dec 2011 at 12:30
Not really. While the server is exposed to an external network, the errors are
generated whenever we open (via POP3) one of the mailboxes on the local James
instance (part of the J-RI). So an external AAAA query is not the case here.
Original comment by nikolai....@gmail.com
on 2 Dec 2011 at 5:09
Getting back on topic with your bug, are you seeing service interruptions with
James? I don't think there is an issue with the DNS server. The DNS server
cannot control someone sending AAAA queries. Is your James server using IP6?
Original comment by gm2...@cerner.com
on 2 Dec 2011 at 1:21
No, not really. The only customization that we have done to the James instance
distributed with the J-RI is enabling SMTPS and POP3S. The Ubuntu 11.10
instance on which the Direct J-RI is running is vanilla as well (no unusual
customizations).
Original comment by nikolai....@gmail.com
on 2 Dec 2011 at 3:32
During the get in ConfigServiceDNSStore it throws DNSException when a query
type isn't implemented. This propagates up to DNSResponder which logs all
DNSExceptions as an ERROR. I've added a check to not log the exception if it's
a not implemented error. It does get logged at DEBUG level in
ConfigServiceDNSStore. Patch attached.
Original comment by tsn...@gmail.com
on 14 Apr 2012 at 8:36
Attachments:
Patch applied/committed and all tests run successfully. Needs validation
testing.
Original comment by gm2...@cerner.com
on 16 Apr 2012 at 2:32
Original issue reported on code.google.com by
nikolai....@gmail.com
on 1 Dec 2011 at 2:17