components-contrib/nameresolution
Alessandro (Ale) Segala 8680e2785a
Local file-based name resolver with SQLite (#3178)
Signed-off-by: ItalyPaleAle <43508+ItalyPaleAle@users.noreply.github.com>
Signed-off-by: Alessandro (Ale) Segala <43508+ItalyPaleAle@users.noreply.github.com>
Co-authored-by: Josh van Leeuwen <me@joshvanl.dev>
Co-authored-by: Bernd Verst <github@bernd.dev>
2023-11-01 15:49:22 -07:00
..
consul Local file-based name resolver with SQLite (#3178) 2023-11-01 15:49:22 -07:00
kubernetes Local file-based name resolver with SQLite (#3178) 2023-11-01 15:49:22 -07:00
mdns Local file-based name resolver with SQLite (#3178) 2023-11-01 15:49:22 -07:00
sqlite Local file-based name resolver with SQLite (#3178) 2023-11-01 15:49:22 -07:00
README.md middleware: changes wasm basic to use waPC (#1833) 2022-09-13 17:12:59 -07:00
metadata.go Local file-based name resolver with SQLite (#3178) 2023-11-01 15:49:22 -07:00
nameresolution.go Local file-based name resolver with SQLite (#3178) 2023-11-01 15:49:22 -07:00
requests.go Remove unused "dns" nameresolver (#3175) 2023-10-13 07:43:57 -07:00

README.md

Name resolution

Name resolvers provide a common way to interact with different name resolvers, which are used to return the address or IP of other services your applications may connect to.

Implementing a new Name Resolver

A compliant name resolver needs to implement the Resolver inteface included in the nameresolution.go file.