Caching with multiple public IP'S, One is wrong!

Question

Caching with multiple public IP'S, One is wrong!

Hi Apple experts,

I am currently running a Mac Mini on 10.12.6 I dont want to upgrade to 10.13 as I prefer the server.app for content caching as opposed to the sharing pane of system in 10.13.

I have 2 public IP addresses that I would like to cache content for. So I set these up in the caching system. Server registered just fine.

Yet when I run AssetCachelocatorUtil from terminal I get incorrect IP address

I see two addresses, One is correct and the other is an old public IP address that we no longer use.

So if I have device that uses the public address thats correct it sees the caching server and will work accordingly.

If i have a device using my other public address it fails to see the caching server and reports its public IP address is outside the configured range.

Im guessing there is a plist file somewhere with the configured public IP addresses? I just cant seem to find it.

Any help on how I can clear this. I'd like to get it working before the iOS and MacOS comes out.

Thanks in advance.

Shaunie

Mac mini, macOS Sierra (10.12.6)

Posted on Sep 7, 2018 4:25 AM

Reply

Answer 1

Sep 7, 2018 7:48 AM in response to shaunfromhull

Below is a partial output from AssetCacheLocatorUtil.

You can see the 2 configured public IP's 92.xxx and 62.xxx

Then on the next line you can see my actual public IP 81.xxx

81.xx is my current and 92.xx is my other current IP. 62.XXX is one that we had a while ago but it hasnt been used in over 2 months and the mac mini has been set to use a single public IP (Its own) until today when I tried to add the second one.

Reply

Answer 2

Sep 8, 2018 2:53 AM in response to More Broccoli Please

Hello More Broccoli Please.

Thanks for your reply. I did find an erroneous entry in DNS for the wayward public IP. I have now correct my DNS server (screenshot below) I have flushed out DNS on my macs and ran DIG -t TXT _aaplcache._tcp.my-domain.com and get back the two correct public IP address. However AssetCacheLocatorUtil is still showing the incorrect public IP. Do I just need to wait for that to update itself?

Thanks in advance for any suggestions.

Reply

Answer 3

Sep 8, 2018 5:01 AM in response to shaunfromhull

Do I just need to wait for that to update itself?

Either wait, or reboot. Your screen shot shows the TTL for the DNS record is 72 hours (259200 seconds) so AssetCacheLocatorUtil (and the rest of the caching system) should re-resolve it on or before Tuesday. If that is too long to wait, reboot the Mac. That forces a refresh.

Reply

Answer 4

Sep 7, 2018 8:14 AM in response to shaunfromhull

AssetCacheLocatorUtil obtains the "configured public IP address ranges" from the DNS TXT record _aaplcache._tcp. Update your DNS server's configuration so that _aaplcache._tcp has the 81.xx and 92.xx addresses.

Reply

Answer 5

Sep 8, 2018 5:23 AM in response to More Broccoli Please

Hey there Broccoli,

Mate you are a genius. I'm not a great on DNS and wondered what that 259200 part was for.

I've rebooted the mac and now everything is as expected.

Thank you very much for your help.

Reply

Caching with multiple public IP'S, One is wrong!

Similar questions