Losing DNS servers

Got a problem with Viscosity or need help? Ask here!

janderso

Posts: 1
Joined: Fri Dec 11, 2009 7:09 am

Post by janderso » Fri Dec 11, 2009 7:25 am
After some searching I seen a thread closed in 2008 regarding this issue, but I was wondering if there is any way to fix this from happening on a network that uses DHCP?

Can viscosity learn of when a DHCP lease is due to expire? Or maybe periodically check for a resolv.conf change?

To prohibit the system DHCP changing my nameservers, my temporary fix has been this:

chflags schg /etc/resolv.conf

But this has some drawbacks.

Otherwise manually forcing viscosity to reconnect fixes it.

The network I am using is not practical to use static addressing, and the pushed down DNS servers provide internal locations to things, so losing these nameservers to system DHCP causes communication to internal locations to start failing.

Other then this I have had no issues with Viscosity. I could see how viscosity may not feel it is viscosity's fault or problem, but nothing else is going to maintain proper DNS servers for viscosity is why I come here in hopes of a permanent solution.

Josh

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Dec 28, 2009 11:18 pm
Hi Josh,

Viscosity should already do this, however you must be using its standard DNS support, as the Alternate DNS support option (under Preferences->Advanced) does not handle DHCP lease changes.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts Page 1 of 1