:property string content: The content of this record
:property bool disabled: Whether or not this record is disabled
- :property bool set-ptr: If set to true, the server will find the matching reverse zone and create a PTR there. Existing PTR records are replaced. If no matching reverse :json:object:`Zone`, an error is thrown. Only valid in client bodies, only valid for A and AAAA types. Not returned by the server. This feature (set-ptr) has been removed in 4.4.0.
+ :property bool set-ptr: If set to true, the server will find the matching reverse zone and create a PTR there. Existing PTR records are replaced. If no matching reverse :json:object:`Zone`, an error is thrown. Only valid in client bodies, only valid for A and AAAA types. Not returned by the server. This feature (set-ptr) was removed in 4.4.0.
Comment
- String
.. deprecated:: 4.2.0
- This setting has been removed in 4.4.0
+ This setting was removed in 4.4.0
Mail address to insert in the SOA record if none set in the backend.
- Default: a.misconfigured.dns.server.invalid
.. deprecated:: 4.2.0
- This setting has been removed in 4.4.0
+ This setting was removed in 4.4.0
Name to insert in the SOA record if none set in the backend.
- Default: 604800
.. deprecated:: 4.2.0
- This setting has been removed in 4.4.0
+ This setting was removed in 4.4.0
Default :ref:`types-soa` expire.
- Default: 3600
.. deprecated:: 4.2.0
- This setting has been removed in 4.4.0
+ This setting was removed in 4.4.0
Default :ref:`types-soa` minimum ttl.
- Default: 10800
.. deprecated:: 4.2.0
- This setting has been removed in 4.4.0
+ This setting was removed in 4.4.0
Default :ref:`types-soa` refresh.
- Default: 3600
.. deprecated:: 4.2.0
- This setting has been removed in 4.4.0
+ This setting was removed in 4.4.0
Default :ref:`types-soa` retry.
When the backend supports it (ISC Bind, Knot, Knot Resolver, PowerDNS Authoritative, PowerDNS Recursor, Unbound, HAProxy, nginx, postfix and many others do), the proxy protocol is the best option.
.. note::
- X-Proxied-For (XPF) was a third option but it has been deprecated for a while, and support has been removed in 2.0.0.
+ X-Proxied-For (XPF) was a third option but it has been deprecated for a while, and support was removed in 2.0.0.
.. _Proxy Protocol:
-------------
.. note::
- XPF support has been removed in 2.0.0.
+ XPF support was removed in 2.0.0.
The experimental XPF record (from `draft-bellis-dnsop-xpf <https://datatracker.ietf.org/doc/draft-bellis-dnsop-xpf/>`_) is an alternative to the use of EDNS Client Subnet which has the advantages of preserving any existing EDNS Client Subnet value sent by the client, and of passing along the original destination address, as well as the initial source and destination ports.