# Point Windows clients at the cache server

Review the local DNS setup recorded for Windows clients using docache.ccmschools.edu.au. Windows DNS and Palo Alto notes are present; the Fortinet section has no configuration steps.

!!!warning Source-derived reference
These notes were recovered from OneNote. Configuration, permissions and operating results have not been freshly verified. Confirm the applicable authority and environment before acting.
!!!

All Windows clients are configured to use Microsoft Connected Cache via a single Intune policy called:

GLOBAL: Update Compliance and Delivery Optimisation.

For this policy to be effective clients must be able to resolve the FQDN docache.ccmschools.edu.au to the local ipaddress of your cache server. When clients cannot resolve that server (whenever they are offsite, connected to a hotspot etc.) they will fall back to the standard update servers.

Docache.ccmschools.edu.au does NOT exist in public DNS records. It needs to be set as a static entry in your local DNS resolver, referencing the local IP address of your cache server.

## Windows DNS Server

Create a Primary DNS zone called **docache.ccmschools.edu.au** and set the default (@) record to the IP of the host. This will ensure you continue to use public DNS to look up other ccmschools.edu.au domain records.

## Palo Alto

If using Palo Alto this is relatively simple. It requires that DNS Proxy is configured on specific VLAN interfaces AND DHCP DNS configured with the subnet gateway as the DNS Server.

[Screenshot retained for review](../../review/Review-status.md#asset-9bdc859f87e3b110f311)

[Screenshot retained for review](../../review/Review-status.md#asset-3cd06034f7d3bc895e78)

[Screenshot retained for review](../../review/Review-status.md#asset-b48e2623cd690310dd4a)

## Fortinet

The source has no Fortinet configuration steps. This branch of the setup remains incomplete.

## Related guidance

- [Topic overview](Introduction.md)
- [Source review status](../../review/Review-status.md)