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.

Sign up for GitHub

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

Jump to bottom

nameservers set as local resolvers may be tested twice #1

Closed
GoogleCodeExporter opened this issue May 27, 2015 · 1 comment
Closed

nameservers set as local resolvers may be tested twice #1

GoogleCodeExporter opened this issue May 27, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1. Set your local nameserver to one of those in namebench.cfg
2. Run namebench.cfg
3. See it tested twice, once really quickly and inaccurately.

Original issue reported on code.google.com by thomas.r...@gmail.com on 20 Jul 2009 at 2:35
@GoogleCodeExporter
Copy link
Author 

We now do dupe-checking based on the nameserver IP.

Original comment by thomas.r...@gmail.com on 17 Aug 2009 at 8:44

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter