call FindServer.refresh(); to refresh DNS-server
settings if e.g. a new DNS server was added to the
system configuration or the status of network interface
has changed.
I didn't apply this directly, but refactored FindServer into
a new class (ResolverConfig) which is a better version, and
has a refresh() method. It doesn't do everything your patch
did, but an application should be able to call
ResolverConfig.refresh() and Lookup.refreshDefault()
(possibly calling Options.refresh() beforehand, if the
servers/search path came from java properties) to update the
configuration used for future lookups.
This will be in the next version, and is in CVS now.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
unified patch against version 1.6.4
Logged In: YES
user_id=63197
I didn't apply this directly, but refactored FindServer into
a new class (ResolverConfig) which is a better version, and
has a refresh() method. It doesn't do everything your patch
did, but an application should be able to call
ResolverConfig.refresh() and Lookup.refreshDefault()
(possibly calling Options.refresh() beforehand, if the
servers/search path came from java properties) to update the
configuration used for future lookups.
This will be in the next version, and is in CVS now.
Thanks!
Ticket moved from /p/dnsjava/patches/6/