stoney

We tried various versions between 2.11.1 and 2.19.6 in the cluster and on client. The behaviour was always that in worked on MacOS but the DNS was broken on different...

Thanks for explaining. I double checked and it is not a general DNS problem. Calling www.google.com works fine in my service. BUT now I understand a bit deeper where my...

I can reproduce this error without mongo db involved. Just call this in app.ts of my service. ``` dns.resolveTxt('MY MONGO DB STRING', (err, record) => { console.log('resolve txt callback'); if...

When i run `telepresence gather-logs` and open the `daemon.log` file: I only see entries for my connect command like `Adding pod subnet` etc. But I do not see any later...

Thanks. So i see an entry for the failing call. ``` 2024-06-17 20:48:39.5487 debug daemon/session/dns/Server : ServeDNS 11919 TXT geeksforgeeks.org. 2024-06-17 20:48:39.5487 debug daemon/session/dns/Server : 11919 TXT geeksforgeeks.org. -> NXDOMAIN...

I added a loop to the start of my app, where I call the dns.resolveTxt function of node and then i get this in the logs: ``` 2024-06-17 20:59:01.6840 debug...

Yes. Without telepresence connection everything works fine. The .org address was just an example. Normally the database is resolved there. When I have telepresence connected the function in the above...

Yes but i think the node dns function is an elemental low level function that shouldnt break when being connected to telepresence right? I want to summarize what I found:...

Why does it even try to resolve the mongo string at the cluster? when running telepresence status I see: `Exclude suffixes: [.com .io .net .org .ru]` Shouldnt this make the...

[Telepresence_DNS_Error.zip](https://github.com/user-attachments/files/15913123/Telepresence_DNS_Error.zip) Thanks a lot. Attached a very small Project. To start the code: Install Node Version Manager and install Node 20. (nvm i 20) Run npm i (npm required) Start...