[ERROR] DNSResponder - Error processing DNS request: Failure while parsing generic record data:

GoogleCodeExporter commented 8 years ago

INFO   | jvm 1    | 2013/06/24 15:30:24 | [ERROR] DNSResponder - Error 
processing DNS request: Failure while parsing generic record data: record does 
not match rrset <org.nhindirect.dns.DNSException: Failure while parsing generic 
record data: record does not match rrset>org.nhindirect.dns.DNSException: 
Failure while parsing generic record data: record does not match rrset
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at 
org.nhindirect.dns.ConfigServiceDNSStore.processGenericRecordRequest(ConfigServi
ceDNSStore.java:281)
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at 
org.nhindirect.dns.ConfigServiceDNSStore.get(ConfigServiceDNSStore.java:186)
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at 
org.nhindirect.dns.DNSResponder.processRequest(DNSResponder.java:105)
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at 
org.nhindirect.dns.UDPServer$RequestTask.run(UDPServer.java:217)
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at java.lang.Thread.run(Unknown 
Source)
INFO   | jvm 1    | 2013/06/24 15:30:24 | Caused by: 
java.lang.IllegalArgumentException: record does not match rrset
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at 
org.xbill.DNS.RRset.addRR(RRset.java:76)
INFO   | jvm 1    | 2013/06/24 15:30:24 |       at 
org.nhindirect.dns.ConfigServiceDNSStore.processGenericRecordRequest(ConfigServi
ceDNSStore.java:276)
INFO   | jvm 1    | 2013/06/24 15:30:24 |       ... 6 more
INFO   | jvm 1    | 2013/06/24 15:30:24 |

What steps will reproduce the problem?
1. Performing a dns request of type "ANY" doesn't return the requested 
information.  But performing a dns request for an "A" record or "NS" record 
work as expected.

What is the expected output? 
; <<>> DiG 9.8.1-P1 <<>> -t ANY @8.8.8.8 directcpsi.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17794
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;directcpsi.com.                   IN      ANY

;; ANSWER SECTION:
directcpsi.com.            3600    IN      MX      10 
directcpsi.com.inbound10.mxlogic.net.
directcpsi.com.            3600    IN      MX      10 
directcpsi.com.inbound10.mxlogicmx.net.
directcpsi.com.            3600    IN      NS      directnameserver.com.
directcpsi.com.            3600    IN      NS      directnameserver.com.
directcpsi.com.            3600    IN      NS      directnameserver.com.
directcpsi.com.            21600   IN      SOA     directnameserver.com. 
directcpsi.com.            3600    IN      A       ipaddress

;; Query time: 88 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Jun 24 16:17:34 2013
;; MSG SIZE  rcvd: 489

What do you see instead?
; <<>> DiG 9.8.1-P1 <<>> -t ANY @8.8.8.8 directcpsi.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 43428
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;directcpsi.com.                        IN      ANY

What version of the product are you using? On what operating system?
This can be tested using linux command line dns tool (dig).
example:
dig -t ANY @8.8.8.8 directcpsi.com

Original issue reported on code.google.com by DaSmart...@gmail.com on 24 Jun 2013 at 8:39

GoogleCodeExporter commented 8 years ago

The ANY type should be supported.  I'm getting ready to start attacking 
outstanding bugs this week and next and will make sure this one is addressed.

Original comment by gm2...@cerner.com on 24 Jun 2013 at 10:55

GoogleCodeExporter commented 8 years ago

The issue has been address (source checked in) and will be release in dns-1.2.2.

The core issue is related to the way the dnsjava RRSet works.  It does not 
allow for multiple DNS response record types to be present within the set.

Unit tests existed that test the ANY type, but only test using the ANY query 
when only one type exists for a specific query question.  A new unit test has 
been added that has multiple record types for the same query question.

Original comment by gm2...@cerner.com on 26 Jun 2013 at 4:44

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

New dig result against fixed version (dns-1.2.2-SNAPSHOT):

$ dig -t ANY direct.securehealthemail.com
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.8.3-P1 <<>> -t ANY direct.securehealthemail.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24424
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;direct.securehealthemail.com.  IN  ANY

;; ANSWER SECTION:
direct.securehealthemail.com. 3599 IN   A   184.72.234.183
direct.securehealthemail.com. 86399 IN  NS  securehealthemail.com.
direct.securehealthemail.com. 3599 IN   SOA securehealthemail.com. 
gm2552\@direct.securehealthemail.com. 1 0 0 0 0
direct.securehealthemail.com. 3599 IN   MX  0 mail1.direct.securehealthemail.com.
direct.securehealthemail.com. 86399 IN  CERT    PKIX 40723 RSASHA1 
MIIEVTCCAz2gAwIBAgIIBPkUbgdf6skwDQYJKoZIhvcNAQEFBQAwbDEp 
MCcGA1UEAwwgRGlyZWN0IFNlY3VyZWhlYWx0aGVtYWlsIFJvb3QgQ0Ex 
CzAJBgNVBAYTAlVTMQswCQYDVQQIDAJNTzEUMBIGA1UEBwwLS2Fuc2Fz 
IENpdHkxDzANBgNVBAoMBkNlcm5lcjAeFw0xMDEyMDMxMzA1NDNaFw0x 
OTAyMTkxMzA1NDNaMIGVMSswKQYJKoZIhvcNAQkBFhxkaXJlY3Quc2Vj 
dXJlaGVhbHRoZW1haWwuY29tMSUwIwYDVQQDDBxkaXJlY3Quc2VjdXJl 
aGVhbHRoZW1haWwuY29tMQswCQYDVQQGEwJVUzELMAkGA1UECAwCTU8x 
FDASBgNVBAcMC0thbnNhcyBDaXR5MQ8wDQYDVQQKDAZDZXJuZXIwggEi 
MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCjuIvE5f6hVHz7YYKe 
Hmu0SEV/GBQhvL36J5dacUGaUNL5genoIXt+YSXfGR8096MDi1oUEdYy 
MyZjwS4c2sOZVSfIpNWLfavOivltkZiM8lPiei+8L67OSKP4jjKg6jk7 
H6m53MTHlZs0lhrzq/Uuhv1N9L1+ek0hZ0Wb7h1lSNh5TDJUHIdNw7cX 
T3i2x8DJVIDBXlKQ9AXDQqAimjANf57MPx2YT0Hzw7NuHK/tLJMaNXeq 
5VSxamuPYKJUCtjE3sMPjC2s7LuDmwsCIgK1zGLwji2tLIygHQNCd04e 
CwQfVrNY0tgwSQmH8fh+BzkLTLzJ9Ow0CFaBcT8kep8TAgMBAAGjgdAw 
gc0wgZ0GA1UdIwSBlTCBkoAUJvo6RlQflVzFanSgzLPMc/+UJ6ihcKRu 
MGwxKTAnBgNVBAMMIERpcmVjdCBTZWN1cmVoZWFsdGhlbWFpbCBSb290 
IENBMQswCQYDVQQGEwJVUzELMAkGA1UECAwCTU8xFDASBgNVBAcMC0th 
bnNhcyBDaXR5MQ8wDQYDVQQKDAZDZXJuZXKCCB++EDlEsK32MB0GA1Ud 
DgQWBBSOZzxSPQopQp6qCkiYp4b9/znnOzAMBgNVHRMBAf8EAjAAMA0G 
CSqGSIb3DQEBBQUAA4IBAQBuoBwPbS7vY4FPGTKYUznz8CtZns6aGLVH 
vT3+UAPZPyWw+/1HKhvubYeOPoGiYzbqvngWmT+rpxOf6k/q0tPiIEMD 
3wHEE6IVXiUPJtqUnBIyPiaVUiIN5at1L3ePeawhIJfbIncrvcX1EPY0 
2YC20s/XxI/PikQDePL2jF+C6b9n0QB54BUxIVd/BEtdD48wc+7ZmPow 
wIf0aqeI90IgjDMkiCqnx1+GT5wPJb0TWIUxBLmM5XYeAWurYLvVLLT/ 
g707ws9IzzqGCNGsSca7ZyBtgmgMsG6OCyk1VRWm7SFYG8REOiaXAJ39 
Bw4i1SEhYOEeQO1uR8rWsZdbcBz1

;; ADDITIONAL SECTION:
securehealthemail.com.  3600    IN  A   184.72.234.183

;; Query time: 6 msec
;; SERVER: 10.184.2.10#53(10.184.2.10)
;; WHEN: Wed Jun 26 11:46:20 2013
;; MSG SIZE  rcvd: 1294

Original comment by gm2...@cerner.com on 26 Jun 2013 at 4:47

JoshuaJeong / nhin-d

[ERROR] DNSResponder - Error processing DNS request: Failure while parsing generic record data: #215