Destination based Service route not working for EDL (External Dynamic List)
7632
Created On 12/07/18 10:20 AM - Last Modified 12/12/18 09:00 AM
Symptom
External Dynamic List interchangeably also known as dynamic block list in earlier releases, is referred to as EDL, and addressed so throughout the document.
User has configured Destination based service route for EDL access under Device->Services->Service Route Configuration->Customize-> Destination
We try to ping the destination from the appropriate source, and the ping completed. However, when an EDL refresh is attempted, we notice that the connection never completes.
Environment
- User has a EDL Service based route configured for all EDL lists, but only for one particular EDL server, we have configured Destination based service route, as it is located behind different network.
- The EDL list is configured using hostname of the server ( FQDN / DNS).
- Destination based service route for the host in question is configured using the resolved IP address, instead of hostname.
Cause
This is expected because of the mismatch in configuration between EDL server in the EDL configuration, and Destination service route configuration.
Resolution
To fix this issue, change one of the configuration, so that 'Destination' in the Destination based service route configuration, and 'Source' in External Dynamic List configuration matches.