DNS provider

The DNS provider maps DNS questions to files. Domains are typed path captures; record files return one answer per line, and raw returns the resolver response summary for a default query.

No credentials are required.

At a glance

Field	Value
Provider id	dns
Default mount	/dns
WASM	omnifs_provider_dns.wasm
Manifest	providers/dns/omnifs.provider.json
Routes	providers/dns/src/lib.rs
Auth	none
Capabilities	cloudflare-dns.com and dns.google for DNS-over-HTTPS; declared memory need 32 MB

Setup

omnifs init dns
omnifs up
omnifs shell

Main paths

/dns/resolvers
/dns/{domain}
/dns/{domain}/{record}
/dns/{domain}/CAA
/dns/{domain}/all
/dns/{domain}/raw
/dns/reverse/{ip}
/dns/@{resolver}/{domain}
/dns/@{resolver}/{domain}/{record}
/dns/@{resolver}/reverse/{ip}

Built-in resolver aliases include Cloudflare and Google. The code supports a default resolver and resolver map, but the provider manifest does not expose a public config schema for them.

Examples

cat /omnifs/dns/resolvers
ls /omnifs/dns/example.com
cat /omnifs/dns/example.com/A
cat /omnifs/dns/example.com/MX
cat /omnifs/dns/@google/example.com/TXT
cat /omnifs/dns/reverse/8.8.8.8

Capability notes

The provider declares DNS-over-HTTPS resolver domains and expected memory needs. Resolver network access still goes through the host capability broker.

Limitations

DNS directories are open and dynamic. ls /omnifs/dns cannot enumerate arbitrary domains.