dnsx returns an additional incorrect cname record when requesting multiple record types #213
-
dnsx version:Tested on 1.0.7/1.1.0 Current Behavior:dnsx returns an additional incorrect cname record, when requesting multiple record types Expected Behavior:dnsx should not return a non existent cname record Steps To Reproduce:Expected results: notice the cname record: "developer.dome9.com.s3-website-us-east-1.amazonaws.com", which is correct. Now run the same query with an additional record type: dnsx now returns an additional cname record, which does not exist: s3-website.us-east-1.amazonaws.com |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
@vgdanieltest looks like that's what has been configured for the input host, see the dig response, there is CNAME record pointing to dig developer.dome9.com
; <<>> DiG 9.10.6 <<>> developer.dome9.com
;; global options: cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14385
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;developer.dome9.com. IN A
;; ANSWER SECTION:
developer.dome9.com. 239 IN CNAME developer.dome9.com.s3-website-us-east-1.amazonaws.com.
developer.dome9.com.s3-website-us-east-1.amazonaws.com. 293 IN CNAME s3-website.us-east-1.amazonaws.com.
s3-website.us-east-1.amazonaws.com. 5 IN A 52.216.100.130
;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Jun 12 19:52:50 IST 2022
;; MSG SIZE rcvd: 164 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ehsandeep, Thank you for the fast response, it's much appreciated. As you can see, the second CNAME record comes from "further down" the chain: s3-website.us-east-1.amazonaws.com is actually the cname record of developer.dome9.com.s3-website-us-east-1.amazonaws.com: I don't think this is the expected dnsx behavior and even if it was, there is still a bug, since you have two requests for the same record with different result sets. |
Beta Was this translation helpful? Give feedback.
-
There are two requests results because you asked to make 2 DNS queries by using You can find the expected result by using: or but if you are using them altogether, this is expected behavior. |
Beta Was this translation helpful? Give feedback.
-
|
@ehsandeep I really don't get why I should expect a different cname result when requesting multiple record types. I'm still checking the same hostname. |
Beta Was this translation helpful? Give feedback.
@vgdanieltest
There are two requests results because you asked to make 2 DNS queries by using
-aand-cnameflags together as each flag makes a new DNS request.You can find the expected result by using:
or
but if you are using them altogether, this is expected behavior.