malformed DNS servers suggestions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 285
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 49
Description
Describe the bug
I had set some malformed DNS servers (the leading dot. was missing), and the OVH manager suggested wrong DNS servers (one missing character at the end of the fqdn) instead of the ones with the leading dot.
The screenshot maybe more explicit.
To Reproduce
Steps to reproduce the behavior:
- Add DNS servers for the zone, without the leading dot (done with terraform, didn't test if from the Manager)
- Go to Manager/Domains/DNS Zone
- See the error
Expected behavior
Manager should suggest existing and correct DNS servers, with leading dot.
Screenshots
Desktop (please complete the following information):
- OS: linux
- Browser: Firefox Nigthly 73.0a1 (2019-12-20) (64-bit)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Manager/Domains/DNS Zone and reproduce the issue by adding DNS servers without the leading dot, as described. Compare the suggested fully qualified domain names with the existing servers; done means the Manager suggests the existing correct names with the leading dot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100