forgot a break statement.

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@ckhardin, could you please let me know what might be wrong in

For example, using host I can obtain data:
host -t SRV testservice._http._tcp.example.com 2a02:2f01:7c05:c000:5da1:9be3:1a3d:81c9
Using domain server:
Name: 2a02:2f01:....
Address: 2a02:2f01:.....
Aliases:

testservice._http._tcp.example.com has SRV record 0 5 8080 dns1.example.com.

@ckhardin, could you please let me know what might be wrong in For example, using host I can obtain data: host -t SRV testservice._http._tcp.example.com 2a02:2f01:7c05:c000:5da1:9be3:1a3d:81c9 Using domain server: Name: 2a02:2f01:.... Address: 2a02:2f01:..... Aliases:

testservice._http._tcp.example.com has SRV record 0 5 8080 dns1.example.com.

Take a packet capture and ensure that the wire sees the query and the response - compare those to the reference host code - if the packets are there, then the issue is likely in the parsing code for the message. There is nothing in the example that stands out as incorrect so this is likely a trace thru some code to figure out the parsing issues.

Also double check the configuration for DNS in the zephyr config and try to make sure all the length and sizes are set larger than the responses coming back. A trade off with zephyr for memory and code size is that the DNS configuration can be limited to messages it can handle in response and that can have unintended consequences.

@ckhardin, could you please let me know what might be wrong in For example, using host I can obtain data: host -t SRV testservice._http._tcp.example.com 2a02:2f01:7c05:c000:5da1:9be3:1a3d:81c9 Using domain server: Name: 2a02:2f01:.... Address: 2a02:2f01:..... Aliases:
testservice._http._tcp.example.com has SRV record 0 5 8080 dns1.example.com.

Take a packet capture and ensure that the wire sees the query and the response - compare those to the reference host code - if the packets are there, then the issue is likely in the parsing code for the message. There is nothing in the example that stands out as incorrect so this is likely a trace thru some code to figure out the parsing issues.

Also double check the configuration for DNS in the zephyr config and try to make sure all the length and sizes are set larger than the responses coming back. A trade off with zephyr for memory and code size is that the DNS configuration can be limited to messages it can handle in response and that can have unintended consequences.

Thanks. I'll keep you updated when I'll have an answer.