[Pound Mailing List] Does Pound cache DNS records beyond their TTL?

I have a need to proxy HTTP requests to a particular URL on my site to
an external service. These requests can be large file uploads, and
Pound seems to do a good job with a service definition like the
following:

Service
    URL "/assemblies"
    BackEnd
        Address api2.transloadit.com
        Port 80
    End
End

The problem is that the vendor, being all modern and cloudy, changes
the IP address of their API endpoint frequently. They have set a
60-second TTL on the A record in DNS, but it seems that Pound does not
honor this: it continues to try to forward requests to the old address
until I restart Pound.

Would you consider this a bug in Pound? Is there a way to make Pound
re-resolve the hostname when its time to live is up?

This is Pound version 2.5.

Thanks,
Vebjorn

--
To unsubscribe send an email with subject unsubscribe to [email protected]
Please contact [email protected] for questions.