dnslookup VS wgcf

I test that IP with https://github.com/ameshkov/dnslookup and it doesn't respond to Do53, DoH nor DoT.

In both FF 113 and FF 114, the proper DoH address works fine, including https://1.1.1.1/dns-query, also try with the servers at https://github.com/curl/curl/wiki/DNS-over-HTTPS, you can verify them through https://github.com/ameshkov/dnslookup

On Windows just extract https://github.com/ameshkov/dnslookup/releases/download/v1.9.1/dnslookup-windows-amd64-v1.9.1.zip and run the terminal from that folder.

So does Chrome says you have a valid cert, or not? That error message comes from AGH, not from Chrome. If Chrome says your cert is valid, then there's no issue. Verify that the DoT (if you use them, if not you can just rely on Cloudflare cert) works with https://github.com/ameshkov/dnslookup

I'm using Technitium, and it requires converting cert to pkcs12, and I think something is wrong here — dnslookup keeps telling me that "tls: failed to verify certificate: x509: certificate signed by unknown authority".

What is your AGH upstream address, and how did you set up Quad9 & Cloudflare? Using dnslookup, compare the result of querying mangadex domain against your AGH instance and Quad9.

Do you have a pc/laptop at hand? Try checking with https://github.com/ameshkov/dnslookup if the DoH/DoT addresses of AdGuard work correctly (ie, filter doubleclick.net etc)

If you directly lookup using https://github.com/ameshkov/dnslookup, does the delay still happens? If not, could be browser/OS caching.

I used https://github.com/ameshkov/dnslookup and the endpoints in https://adguard-dns.io/kb/general/dns-providers/#cisco-opendns, all of them resolve my domain correctly. Could be region specific though.

I can successfully create wg profiles using wgcf and connect to Cloudflare servers.

I normally don't install Cloudflare Warp client. I just generate WireGuard profile of Cloudflare Warp using wgcf and connect using WireGuard.

Divirta-se: https://github.com/ViRb3/wgcf.

I'm using https://github.com/ViRb3/wgcf and it works fine. I had to change the "Endpoint" line in the config file tho: Endpoint = 162.159.193.5:2408

I'm using Cloudflare's Zero Trust Tunnel with a WireGuard configuration obtained from "https://github.com/ViRb3/wgcf". This configuration includes my private key and DNS settings.

All of my test and deploy scripts have to be encapsulated within docker containers or they’re not compatible. The thing is WARP seems to require some system resources that aren’t allowed from inside a containerwhen it sets up its network. I’ve also tried WCGF, which can run in containers but doesn’t have support for cloudflare Teams.

If nothing works, generate a WireGuard config file with WGCF: https://github.com/ViRb3/wgcf

Generate a wireguard profile for 1.1.1.1 WARP, then load that profile into your scale WireGuard UI