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

namebench should exclude consistently terrible system DNS servers #35

Closed
GoogleCodeExporter opened this issue Apr 6, 2015 · 2 comments
Closed

namebench should exclude consistently terrible system DNS servers #35

GoogleCodeExporter opened this issue Apr 6, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

If a system DNS server has a consistent history of failures (say, 3+), it 
should be canned instead of 
hanging around and slowing all of the tests down. Normal nameservers get canned 
on the first error 
already.

Original issue reported on code.google.com by helixblue on 5 Dec 2009 at 7:05
@GoogleCodeExporter
Copy link
Author

Original comment by tstromb...@google.com on 7 Dec 2009 at 3:32

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author 

Fixed in 1.0.2.

Original comment by tstromb...@google.com on 8 Dec 2009 at 7:35

  • 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-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter