===========
DNS Caching
===========

As of 6.4, connected IPs can no longer be configured to perform DNS caching natively.
Instead, a bond can be configured with a DNS caching service, which can then be bound to connected IPs.

Unlike all other services, a bond can only have one DNS caching service, with the service instead binding to multiple connected IPs.

Configuring a DNS Caching Service
------------------------------------

Connected IPs
++++++++++++++++++

.. note::
    For historical reasons, DHCP services can also be configured to perform DNS caching for a particular connected IP.
    Configuring any `DNS caching options on a DHCP service <./dhcp.html#dns-caching-dns-servers-optional>`__ will conflict
    with the stand-alone DNS caching service for that connected IP.

Which connected IPs the DNS caching service will bind to.

DNS requests to the selected connected IPs will be forwarded to upstream DNS servers and cached.
If DNS servers are given below, they will be used as the upstream servers. If they are not given, the bonder's own DNS servers will be used.


DNS servers (optional)
+++++++++++++++++++++++

Here, addresses may be specified as upstream DNS servers.
