TTL set to 60sec the default they have. The ip/domain was correct on the home side where it refreshed probably with the reboot. On the office side which I did not reboot as I try not to reboot unless I have to was incorrect. Atleast I know to look at logs from both sides in the future and it will alleviate some madness in troubleshooting.
On Fri, Jul 23, 2010 at 1:01 AM, Chris Buechler <[email protected]> wrote: > > > On Fri, Jul 23, 2010 at 1:51 AM, Paul Peziol <[email protected]> wrote: > >> I will update this for others incase they run across this. Had some time >> to look at this again. The ip was showing correctly in the logs on the >> dynamic side at home.Didnt think to compare the logs from the office side. I >> looked at the logs on the pfsense in the office and noticed a different ip >> in the logs. I did a ping in pfsense from the office and it was going to the >> wrong ip address. Even though the dyndns account had the correct ip updated >> to it, the pfsense in the office still had the old ip address cached in the >> dns and didnt refresh correctly. A DNSMASQ restart corrected the issue and >> tunnels came right up. Hopefully this helps someone in the future. >> > > Check the TTL on your dyndns account, that indicates it's much longer than > it should be. Normally it's a 30-60 second TTL, which means it'll pick it up > within 1 minute or less. It won't cache anything past TTL. > >
