Thomas Merz
Thomas Merz
@riyadhalnur , did you found some time to have a look at my issue?
@jvns , do you agree to close this issue, if there's no chance to decode any DNSSEC packages? So I misunderstood the output "Error…" 🤷🏻♂️
@badnetmask - Well, it's not taking so long to respond. One second would be very, very intolerable to deal with… I'm used up to 10-20 ms. ``` 17:20 $ sudo...
@jvns - with wireshark I can see in the pcap file that there's a response: Sending pcap file directly to you, because I'm not sure if it may contain some...
Also with latest 0.1.1. as soon as I **turn on my VPN all queries have "no response"**… 😢 And when VPN is off almost all queries have a response again...
``` timestamp query name server IP elapsed response Error parsing DNS packet: Failed to parse DNS packet: Could not decode QType: 65 Error parsing DNS packet: Failed to parse DNS...
Hi @jvns , do you have any idea regarding this issue? With the latest release of dnspeep this is **still an issue** on my Macbook when **Cisco VPN** is activated...
Ok, feel free to ping me, if you need some more input from me.
Are there any news regarding this? In https://github.com/jvns/dnspeep/issues/26 it took me some time to get the root cause (process) that is querying so much nameservers (solution: it was my regular...
Same here with version 1.12.0 and https://healthchecks.io 😢 The [standalone uptime tracker](https://github.com/henrywhitaker3/uptime-tracker) works fine - but not this integration here.