DNS-over-HTTPS Proxy

How It Works

The proxy is triggered by a domain suffix in the request path. The first segment is the access password; everything after it is the upstream DoH server you define.

• 1
  Password first Request /doh.<pwd>/... — the first segment after /doh. must equal your access token.
• 2
  Verify before proxy Wrong / missing password → a random UUID is returned and the request is never forwarded.
• 3
  Path-based routing After <pwd>/, the rest <domain>/<path> is rewritten to https://<domain>/<path>.
• 4
  Protocol passthrough GET uses application/dns-json; POST uses application/dns-message (wire format). CORS enabled.

The password is the first segment after /doh., before your custom DoH address. Wrong password → random UUID, no proxy.

GET JSON API (dns-json)

curl "https://glm5.331319.xyz/doh.<pwd>/alidns.com/dns-query?name=example.com&type=A"

POST Wire Format (dns-message)

# Resolve example.com AAAA
dog --type AAAA example.com --dns "https://glm5.331319.xyz/doh.<pwd>/alidns.com/dns-query"

# Or with curl + binary body
curl -X POST "https://glm5.331319.xyz/doh.<pwd>/alidns.com/dns-query" \
     -H "Content-Type: application/dns-message" \
     --data-binary @dns_request.bin

ANY Wrong / Missing Password

# Any path that does NOT start with /doh.<correct-pwd>/ returns a UUID
curl "https://glm5.331319.xyz/doh.wrong-pwd/alidns.com/dns-query?name=example.com"
# -> 200  "f47ac10b-58cc-4372-a567-0e02b2c3d479"

curl "https://glm5.331319.xyz/doh.<pwd>/alidns.com/dns-query"
# -> 200  (proxied)  {"Status":0, ...}