ignoramous

> Is that a bug or was this behaviour changed on purpose? On purpose: #1466 > If done on purpose, what's the reasoning behind this? Some folks have `.local`, `.lan`,...

Thanks. > Related feature request from Matrix (by @deknos82:matrix.org). > something lik, please reserver *.lan, *.wan, *.man, *.link, *.site, *.multi, *.cast, and *.{lan,wan,man,link,multi.site}.cast? Do they want these (uncommon?) domains to...

Gotcha. > Both want the ability to have them sent to system DNS Covered by #1153 > the ability to customize said endpoint... To send certain top-level domains to specific...

> That means somehow local IPs could bypass my vpn. Only if you turn ON *Do not route Private IPs* in *Configure* -> *Network*. Otherwise, this shouldn't happen. > access...

> This entry is deactivated and greyed out because of Lockdown-Mode. >> Only if you turn ON Do not route Private IPs in Configure -> Network. Otherwise, this shouldn't happen....

Remove IPv6 from *Peer Endpoint*, if present and see if WireGuard then works? If so, you're likely hitting #1483 (which we will release a fix in a day or so).

Thanks. Allowing arbitrary upstream DNS per domain will end up confusing the user (due to the number of possible configurations). Is this use-case better covered by #1153?

> hope custom rules to blackhole all domains with "epdg" can do the trick By convention (or standard), do wifi-calling domains have `epdg` in its subdomain? btw, Rethink doesn't support...

[`https://matrix.to/#/!jrTSpJiEkFNNBMhSaE:matrix.org`](https://matrix.to/#/!jrTSpJiEkFNNBMhSaE:matrix.org)? I just tried it and it did work for me. Will you see if this new one works: [`https://matrix.to/#/#rethinkdns:matrix.org`](https://matrix.to/#/#rethinkdns:matrix.org)?

I am not sure if the room is closed due to spam... /cc: @PoneyClairDeLune