Recents Post
Discovery
Cache Discovery FAQ
How Does Cache Discovery Work?
PeerCache™ is designed to work transparently with supported peer-to-peer applications through an automated DNS-based discovery process.
When a compatible P2P client starts a download, it checks for the existence of a designated cache server by querying specific DNS entries configured by the Internet Service Provider or network administrator.
To enable PeerCache™, the ISP simply creates the appropriate DNS entry pointing to the PeerCache server’s IP address.
Once configured:
- Compatible P2P clients automatically discover and use the cache
- No manual configuration is required by end users
- No modifications are needed to the P2P client software
- Cache support is enabled by default in supported applications
Supported Protocols
Automatic PeerCache™ discovery is currently supported for clients using:
- FastTrack Protocol (KaZaA, iMesh, Grokster)
- Edonkey2k Protocol
How Does PeerCache Work with P2P Applications?
Each supported protocol uses a dedicated DNS lookup entry.
DNS Entries by Protocol
| Protocol | DNS Entry |
|---|---|
| FastTrack (KaZaA, iMesh, Grokster) | cache.p2p |
| Edonkey2k | edcache.p2p |
Cache Discovery Process
The client application first attempts to resolve the global cache hostname:
cache.p2pIf the lookup fails, the client progressively searches within the local domain hierarchy.
For example, if the client hostname is:
client.adsl.isp.comThe client attempts to resolve:
cache.p2p
cache.p2p.adsl.isp.com
cache.p2p.isp.comThe first successfully resolved hostname is automatically used as the active cache server.
This intelligent lookup process allows ISPs to deploy localized cache infrastructures efficiently across multiple regions and network segments.
How Long Does Cache Discovery Take?
To minimize excessive DNS traffic, compatible P2P clients typically attempt cache discovery once every 48 hours.
As a result:
- Full cache adoption generally occurs within approximately 2 days
- Cache utilization grows gradually as users reconnect and perform new lookups
- Traffic levels may fluctuate depending on user activity and P2P demand
Why Is My Client Not Using the Cache?
If the DNS entries are configured correctly but the client is still bypassing the cache, the most common reason is that the client recently performed a cache lookup within the last 48 hours and either:
- Did not locate a valid cache server
- Did not receive a valid license response
In such cases, the client waits until the next scheduled discovery cycle before retrying.
Resetting the KaZaA Cache Discovery Timer
To force KaZaA to immediately retry cache discovery for testing purposes, set the following Windows Registry value to zero:
[HKCU\Software\Kazaa\Transfer]
"CacheDiscoveryTime"=dword:00000000This resets the internal 48-hour discovery timer.
Resetting the Edonkey / Overnet Cache Discovery Timer
For Edonkey or Overnet clients, delete the following file from the application installation directory:
JPCPlugin.iniThe client will then perform a fresh cache discovery attempt on the next launch.
Verifying Cache Detection in Edonkey Clients
To confirm whether an Edonkey or Overnet client successfully detected the cache, check the contents of:
JPCPlugin.iniIf the cache IP address listed in the file is not:
0.0.0.0then the client has successfully discovered and connected to the PeerCache™ server.
