What I've been doing and trying with the Apple TV to work around this issue.
Submitted a bug report for this some time ago, as per usual.. "Engineering has determined that your bug report is a duplicate of another issue and will be closed."
You name it, I've probably tried it. Wired/WiFi/Static IP's/Different networks/Isolated hotspot network testing/Resetting/Restoring etc etc. The problem has remained through every update. So i restored it a couple of days ago for the i don't know how many times, gave it a new name, restarted Airports (all network hardware is Apple and one is the DHCP server for other network devices, 95% have static IP's however). All was well.. until I come home a couple hours later that day to find that it has counted its way up to (110) in this time already.
Fuming intensifies
Checking all bonjour services on my network, theres 5 bonjour services which it has.
Under different services it has different names.
| Bonjour Service | Responsibility/Function | Bonjour Name |
|---|
| _airplay._tcp. | AirPlay | Apple TV (30) |
| _appletv-v2._tcp. | AirPlay and Home Sharing related | Apple TV |
| _raop._tcp. | AirTunes/Remote Audio Output Protocol | Apple TV (110) |
| _sleep-proxy._tcp. | Sleep Proxy Service | Apple TV |
| _touch-able._tcp. | Remote Control Protocol for Watch/iOS Deivces | Apple TV |
This explains why;
But it doesn't explain why I'm not seeing Apple TV (30) for the _airplay._tcp. bonjour service, as all your usual AirPlay services are being shown already, not sure what app/function uses the _airplay._tcp. service.
All names are tied to its ethernet IP. As I'm writing this my iTunes AirPlay is stopping/starting every 5 minutes and during the time its hanging the Apple TV bonjour service _raop._tcp. increases its number in brackets by 1, so I'm currently up to 115.. (I started at 110 when i started writing this).
Thinking i had tried everything i could, a crazy suggestion came about. Add a space or two to the end of the name of it, tried it i did, I've not had a problem with the name since. Don't ask me why this is happening, i have no idea. I assumed it would just over write its own name on the network and begin adding numbers again but it just has not happened under its normal usage.