ronysebastian / nhin-d

Automatically exported from code.google.com/p/nhin-d
0 stars 0 forks source link

J-RI DNS Server keep posting an error #169

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run the J-RI
2. Tail the log for the DNS Server
3. Check any mailbox in James (POP3 list, etc) 

What is the expected output? What do you see instead?

INFO   | jvm 1    | 2011/11/30 14:56:57 | [ERROR] DNSResponder - Error
processing DNS request: Query Type
28 not implemented <org.nhindirect.dns.DNSException: Query Type 28 not
implemented>org.nhindirect.dns.DNSE
xception: Query Type 28 not implemented
INFO   | jvm 1    | 2011/11/30 14:56:57 | at
org.nhindirect.dns.ConfigServiceDNSStore.get(ConfigServ
iceDNSStore.java:209)
INFO   | jvm 1    | 2011/11/30 14:56:57 | at
org.nhindirect.dns.DNSResponder.processRequest(DNSRespo
nder.java:105)
INFO   | jvm 1    | 2011/11/30 14:56:57 | at
org.nhindirect.dns.UDPServer$RequestTask.run(UDPServer.
java:206)
INFO   | jvm 1    | 2011/11/30 14:56:57 | at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
ThreadPoolExecutor.java:886)
INFO   | jvm 1    | 2011/11/30 14:56:57 | at
java.util.concurrent.ThreadPoolExecutor$Worker.run(Thre
adPoolExecutor.java:908)
INFO   | jvm 1    | 2011/11/30 14:56:57 | at
java.lang.Thread.run(Thread.java:662)

What version of the product are you using? On what operating system?

Direct J-RI 1.2, Ubuntu 11.10

Original issue reported on code.google.com by nikolai....@gmail.com on 1 Dec 2011 at 2:17

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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:

GoogleCodeExporter commented 9 years ago
Patch applied/committed and all tests run successfully.  Needs validation 
testing.

Original comment by gm2...@cerner.com on 16 Apr 2012 at 2:32