Gargoyle Forum

Hey there!

Our company has been using gargoyle for awhile, loving it, however we've run into a problem.

We do web development and whenever we're in the process of uploading a website, namely, changing name servers of a domain, the router isn't updating the propagation change for several days.

Whenever we change the name server, check it in whatismydns.net, it shows that it's changed through the world successfully, but through our router it doesn't update.

We've isolated the issue to be gargoyle, as when we connect directly to the modem the website loads with the new name server change, just like it should.

This issue has occurred with dozens of websites, and it's reached the point to where it's just not feasible to keep tethering a connection through our phones.

Does anyone know whats going on here? Is it something to do with the dnsmasq cache size?

Gargoyle and Openwrt both use dnsmasq to cache DNS records. The amount of time any given DNS record is cached is set by the Authoritative DNS server (ie under your control).

You might read here http://dyn.com/blog/dyn-tech-everything ... bout-ttls/ It looks like a TTL of 1 day is common.

From the command line you can issue "killall -s SIGHUP dnsmasq" which will cause dnsmasq to reload its cache immediately.

You can select any number of other DNS servers in the Gargoyle configuration page if you would like to use them instead. OpenDNS and GoogleDNS servers are used by some. dnsmasq is used by default. But all DNS servers should have this same issue since the TTL is set by you when you create the original DNS record.