Re-adding tirapan.top

[demarcush]

Problem with caddy and h3:
caddyserver/caddy#5086 (comment)

Problem with DoH proxy:
https://github.com/m13253/dns-over-https?tab=readme-ov-file#known-issues

So unless anyone can suggest a way to simultaneously have the two of them (https server and DoH proxy) listen on 443, all I can do is wait for them to get fixed/implemented.

[jedisct1]

Not sure what the compatibility issues are with the DoH server you linked. Maybe try doh-server?

[demarcush]

Migrated to doh-proxy. Thank you!
Still, don't leave me out only because I don't have http3 support. 🙏

[jedisct1]

HTTP/2 is fine. HTTP/3 is blocked in many places.

[demarcush]

HTTP/2 is fine. HTTP/3 is blocked in many places.

Yes, finally figured out that dnscrypt-proxy tries to connect to the service via http3 if alt-svc advertises it. With caddy not being able to reverse proxy http3 connections, just figured out it would be better to shut off h3 conns altogether until they add that feature to their reverse_proxy module.
Thank you for your patience.

[jedisct1]

QUIC and HTTP/3 are finally coming to the Go standard library: https://pkg.go.dev/golang.org/x/net/quic

This is going to make it way easier for software like Caddy to support these.

[demarcush]

I guess not until 0-RTT is supported. It needed 0-RTT for it to perform the query on IPv4.
Anyway, can you point me to anything that tells me how to become an ODOH target? Is using doh-proxy with -O flag enough? And how can I test it?

[jedisct1]

@demarcush All you need is make sure that queries for /.well-known/odohconfigs are also routed to the DoH server.

You can then test with the stamp sdns://BQcAAAAAAAAAC3RpcmFwYW4udG9wEC9ub21lbi1xdWFlc2l0dW0 and an ODoH relay.

[demarcush]

Done and tested. Will open a new PR for adding it to odoh targets.