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

Hi Vebjorn,

the DNS resolution will be done only once at startup. That means IP
address changes will not be honoured by Pound  during runtime
(regardless of any TTL) . You have to restart Pound. This is not a bug
it's a feature, as DNS lookups are expensive. Somebody has written a
patch against Pound 2.5. Perhaps this patch is working for you ...

Patch:
http://www.apsis.ch/pound/pound_list/archive/2011/2011-05/1305196926000/index_html?fullMode=1#1305196926000
Mailinglist-Thread:
http://www.apsis.ch/pound/pound_list/archive/2011/2011-06/1308931610000/index_html?fullMode=1

Hope this helps :-)

Kind regards,
Leo


On 10/23/2013 08:57 PM, Vebjorn Ljosa wrote:
> 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.
>


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