-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Change one of the test domains for the DNS tests #13333
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
Conversation
LocalStack Community integration with Pro2 files ± 0 2 suites ±0 33s ⏱️ - 1h 58m 33s Results for commit 6515127. ± Comparison against base commit 4952b82. This pull request removes 4892 tests. |
simonrw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good idea, thanks. A ticking time bomb that went off!
There are other mentions of something.org in test_dns_server_soa_record_suffix_matching, is it worth changing those to use example.org as well?
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 9m 22s ⏱️ Results for commit 6515127. |
I saw those, but they are only the value of the SOA entry, not the name queried, so I did not change it. It should not come into contact with the something.org nameservers, so I think we should be safe 👍 |
Motivation
Recent test failures showed the
foo.something.orgdomain we used for testing resolving to an unexpected IP address. It seems the domain owner, a domain reseller, started resolving this domain to some IP.Even though this seems to have changed again since, we should not take the risk in the future.
Fixes ENG-104
Changes
something.orgtoexample.orgin tests querying the name servers of a domain.Tests
Related