Get desktop application:
View/edit binary Protocol Buffers messages
This message contains the configuration for the DNS Filter if populated from the control plane
Used in:
Control how many times Envoy makes an attempt to forward a query to an external DNS server
Fully qualified domain names for which Envoy will respond to DNS queries. By leaving this list empty, Envoy will forward all queries to external resolvers
This field is deprecated and no longer used in Envoy. The filter's behavior has changed internally to use a different data structure allowing the filter to determine whether a query is for known domain without the use of this field. This field serves to help Envoy determine whether it can authoritatively answer a query for a name matching a suffix in this list. If the query name does not match a suffix in this list, Envoy will forward the query to an upstream DNS server
This message contains a list of IP addresses returned for a query for a known name
Used in:
This field contains a well formed IP address that is returned in the answer for a name query. The address field can be an IPv4 or IPv6 address. Address family detection is done automatically when Envoy parses the string. Since this field is repeated, Envoy will return as many entries from this list in the DNS response while keeping the response under 512 bytes
Used in:
Define a list of addresses to return for the specified endpoint
Define a cluster whose addresses are returned for the specified endpoint
Define a DNS Service List for the specified endpoint
This message defines a service selection record returned for a service query in a domain
Used in:
The name of the service without the protocol or domain name
The service protocol. This can be specified as a string or the numeric value of the protocol
The service entry time to live. This is independent from the DNS Answer record TTL
The list of targets hosting the service
Define a list of service records for a given service
Used in:
Specify the service protocol using a numeric or string value
Used in:
Specify the protocol number for the service. Envoy will try to resolve the number to the protocol name. For example, 6 will resolve to "tcp". Refer to: https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml for protocol names and numbers
Specify the protocol name for the service.
Specify the target for a given DNS service [#next-free-field: 6]
Used in:
Specify the name of the endpoint for the Service. The name is a hostname or a cluster
Use a resolvable hostname as the endpoint for a service.
Use a cluster name as the endpoint for a service.
The priority of the service record target
The weight of the service record target
The port to which the service is bound. This value is optional if the target is a cluster. Setting port to zero in this case makes the filter use the port value from the cluster host
Used in:
A domain name for which Envoy will respond to query requests. Wildcard records are supported on the first label only, e.g. ``*.example.com`` or ``*.subdomain.example.com``. Names such as ``*example.com``, ``subdomain.*.example.com``, ``*subdomain.example.com``, etc are not valid wildcard names and asterisk will be interpreted as a literal ``*`` character. Wildcard records match subdomains on any levels, e.g. ``*.example.com`` will match ``foo.example.com``, ``bar.foo.example.com``, ``baz.bar.foo.example.com``, etc. In case there are multiple wildcard records, the longest wildcard match will be used, e.g. if there are wildcard records for ``*.example.com`` and ``*.foo.example.com`` and the query is for ``bar.foo.example.com``, the latter will be used. Specific records will always take precedence over wildcard records.
The configuration containing the method to determine the address of this endpoint
Sets the TTL in DNS answers from Envoy returned to the client. The default TTL is 300s