DNS Role on Gravity

Zones

Mon, 01 Jan 0001 00:00:00 +0000

Handlers

The order of handler matters; Gravity will send a query to each handler in the order they are configured until a response is returned.

The handler configuration consists of a list of individual handler configurations. All list entries require a type attribute which must match one of the headers listed below. For example:

- type: forward_blocky
 to:
 - 8.8.8.8
 cache_ttl: 3600
- type: forward_ip
 to:
 - 8.8.8.8

- type: memory
- type: etcd

`etcd`

Attempt to reply to query by looking for records in etcd. Keep in mind that because this is configured on zone level, this handler will only look for matching records in the current zone.

Hooks

Mon, 01 Jan 0001 00:00:00 +0000

Hook Methods

`onDNSRequestBefore(request)`

Called before the DNS response is generated.

request: See https://pkg.go.dev/beryju.io/gravity/pkg/roles/dns/utils#DNSRequest

`onDNSRequestAfter(request, response)`

Called after the DNS response is generated.

request: See https://pkg.go.dev/beryju.io/gravity/pkg/roles/dns/utils#DNSRequest
response: See https://pkg.go.dev/github.com/miekg/dns#Msg

Environment

`gravity` Object

`log(msg: any)`

Logs a message to the stdout of the Gravity node this hook is run on.

`node: string`

The identifier of the node this hook is run on.

`version: string`

The version of Gravity on the node this hook is run on.

Role configuration

Mon, 01 Jan 0001 00:00:00 +0000

port: The port the DNS server listens on (defaults to port 53).

DNS Role on Gravity

Zones

Handlers

etcd

Hooks

Hook Methods

onDNSRequestBefore(request)

onDNSRequestAfter(request, response)

Environment

gravity Object

log(msg: any)

node: string

version: string

Role configuration

`etcd`

`onDNSRequestBefore(request)`

`onDNSRequestAfter(request, response)`

`gravity` Object

`log(msg: any)`

`node: string`

`version: string`