07-12-2024, 11:18 AM
(This post was last modified: 07-12-2024, 04:06 PM by Justin Case.
Edit Reason: Resolved original DNS response problem.
)
[EDIT] I've solved this now - found wireshark installed on the VM and found the problem - missing length byte at the beginning of the TXT record. For some reason I didn't think wireshark ran on XP but I found it there and fixed it now. But if anyone can still help with the problem below I'd be grateful!!
Hi
Ages ago from somewhere, I found an example for using Indy10's TIdDNSResolver component.
Using that component isn't much of a problem however I'm trying to debug why a TXT record that is served from my server, is misunderstood and coming through garbled. Having this demo on my desktop I thought I'd use it.. but I can't find the source code anywhere in order to debug what is coming in from my dns server.
The demo's main form looks like this:
![[Image: screenshot-1612.jpg]](https://i.postimg.cc/661R33BW/screenshot-1612.jpg)
Does this ring any bells with anyone?
It's not one of the indy demos and isn't on the indy github either. I've been prowling around my hard drives but cannot locate it anywhere - all i have is the executable.
Thanks,
JC
Hi
Ages ago from somewhere, I found an example for using Indy10's TIdDNSResolver component.
Using that component isn't much of a problem however I'm trying to debug why a TXT record that is served from my server, is misunderstood and coming through garbled. Having this demo on my desktop I thought I'd use it.. but I can't find the source code anywhere in order to debug what is coming in from my dns server.
The demo's main form looks like this:
Does this ring any bells with anyone?
It's not one of the indy demos and isn't on the indy github either. I've been prowling around my hard drives but cannot locate it anywhere - all i have is the executable.
Thanks,
JC