Sophos Central Public Update Cache using FQDN

Dear GlennSen 
Any Update on this please
I have almost 60 endpoints don't take update

Hello,

you could try to solve this with your DNS. Give the server only a public name and the corresponding ip, depending on your network at that site.

Hi Philip
Thanks for answering

"Give the server only a public name and the corresponding ip"
just to make sure
do you mean i have to make the hostname of my server "cache.public.com" so it will be resolvable from the rest of endpoint ?
and this way the server can't be in AD domain am i right ? because if it's in a AD domain its hostname will be cache.something.local

Hi Philip
Thanks for answering

"Give the server only a public name and the corresponding ip"
just to make sure
do you mean i have to make the hostname of my server "cache.public.com" so it will be resolvable from the rest of endpoint ?
and this way the server can't be in AD domain am i right ? because if it's in a AD domain its hostname will be cache.something.local

Hello Ahmad,

it is not necessary to give a domain memberserver an internal domain name. In fact, it has only be able to reach the ADS controller as the first DNS resolver and to have the reqiured ports open to reach the ADS services.

So you could have:

ad1.mydomain.local and ad2.mydomain.local as your ADS/DNS

and cacheserver.public.com with a separate DNS-record inside your local DNS-systems.

Be aware, that all other resources in your public domain (in our example xxx.public.com) must be resolved by your internal DNS server, when querying form internal at your main site. But this is little to no effort and one time only.