I run my self hosted WireGuard server that points to my subdomain in order to connect so that way in case my IP changes I don’t have to worry loosing connection. The problem is I don’t think I should be trusting Cloudflare with all my traffic even though I am not doing anything particularly sensitive. After all, the point of self hosting is to keep your stuff private.
If you’re going to connect to a subdomain on a domain who’s DNS is hosted at Cloudflare you’re going to have to diasable the proxying of the subdomain for it to work anyway so Cloudflare won’t ever see your traffic. Traffic will be direct from client to server.
Additionally WG traffic is inscrutable so even if you routed traffic through them (which you can do if you really, really want to) they wouldn’t be able to see the contents and could only infer your actions through the metadata they could collect (time of connection, amount of data etc).
If the connection is proxied, it’s fine. If it’s a DNS record, I’d probably remove it and just connect to your vpn via your ip.
Having it unproxied in a dns record just makes it easier for domain dns record dumpers to find it and attack it for no reason other than they can.
Limit visibility. It’s not a complete solution to it, but it does help.
Regarding giving cloudflare any info… you’re running a vpn lol how would they possibly know what you’re doing? All your traffic is encrypted. All they know is you connect to vpn.doma.in and transfer data to it.
can anyone explain to me a noob, while this answer was downvoted?
I thought about using cloudflare instead of using my direct ip and the first thing that came to my mind was that it would be more visible to external visitors.
It doesn’t matter if the VPN service I have deployed is from Cisco or OpenVPN, I have to configure it for a given set of requirements and in order to do that reading documentation is necessary.