Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Successful name lookups cached forever #3261

Closed
cyberduck opened this issue Jun 21, 2009 · 6 comments
Closed

Successful name lookups cached forever #3261

cyberduck opened this issue Jun 21, 2009 · 6 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

bierbo24 created the issue

I connect to a FTP server using DNS everything works fine.
Later when I try to reconnect to this FTP it doesn't work.

Cyberduck tries to reconnect to the old IP (it seems that the old IP is cached forever).
I have to close Cyberduck to be able to connect again to this server.

This wouldn't be such a big problem, but the IP of this server changes every 8 hours.
So everyday I have to tell a lot of people, who also use Cyberduck, because it is the best FTP client, that the server isn't down and they have to close Cyberduck.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This was discussed in #2839 and #2606 before. We set the networkaddress.cache.ttl property to 10 seconds but that does not seem to work. Will have to investigate further.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please try clearing the DNS cache held by OS X using Terminal.app

dscacheutil -flushcache

@cyberduck
Copy link
Collaborator Author

anonymous commented

Clearing the DNS cache doesn't seem to help

@cyberduck
Copy link
Collaborator Author

bierbo24 commented

It seems to be fixed with newest version and Snow Leopard

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 bierbo24]:

It seems to be fixed with newest version and Snow Leopard

I suppose this is now working due to the switch to Java 6.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

#4061 closed as duplicate.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants