Skip to main content
Server Fault

Return to Question

replaced http://serverfault.com/ with https://serverfault.com/
Source Link
Community Bot
Community Bot
  • 1

I have a question here http://serverfault.com/questions/670436/how-do-i-use-tls-https-using-dane-dnssechttps://serverfault.com/questions/670436/how-do-i-use-tls-https-using-dane-dnssec IMO it's incorrectly marked as a duplicate. One question explains the problem and the expected results. The other was poorly worded and confused readers into locking it because they didn't understand it. Why are we locking both so no answers are possible? If you read both you'll see they are different questions trying to solve the same question and not a phrasing or a duplicate.

I have a question here http://serverfault.com/questions/670436/how-do-i-use-tls-https-using-dane-dnssec IMO it's incorrectly marked as a duplicate. One question explains the problem and the expected results. The other was poorly worded and confused readers into locking it because they didn't understand it. Why are we locking both so no answers are possible? If you read both you'll see they are different questions trying to solve the same question and not a phrasing or a duplicate.

I have a question here https://serverfault.com/questions/670436/how-do-i-use-tls-https-using-dane-dnssec IMO it's incorrectly marked as a duplicate. One question explains the problem and the expected results. The other was poorly worded and confused readers into locking it because they didn't understand it. Why are we locking both so no answers are possible? If you read both you'll see they are different questions trying to solve the same question and not a phrasing or a duplicate.

added 125 characters in body
Source Link
user274
user274

I have a question here http://serverfault.com/questions/670436/how-do-i-use-tls-https-using-dane-dnssec IMO it's incorrectly marked as a duplicate. One question explains the problem and the expected results. The other was poorly worded and confused readers into locking it because they didn't understand it. Why are we locking both so no answers are possible? If you read both you'll see they are different questions trying to solve the same question and not a phrasing or a duplicate.

I have a question here http://serverfault.com/questions/670436/how-do-i-use-tls-https-using-dane-dnssec IMO it's incorrectly marked as a duplicate. One question explains the problem and the expected results. The other was poorly worded and confused readers into locking it because they didn't understand it. Why are we locking both so no answers are possible?

I have a question here http://serverfault.com/questions/670436/how-do-i-use-tls-https-using-dane-dnssec IMO it's incorrectly marked as a duplicate. One question explains the problem and the expected results. The other was poorly worded and confused readers into locking it because they didn't understand it. Why are we locking both so no answers are possible? If you read both you'll see they are different questions trying to solve the same question and not a phrasing or a duplicate.

Source Link
user274
user274

Why lock a question because a poorly worded locked duplicate with no answers exist?

I have a question here http://serverfault.com/questions/670436/how-do-i-use-tls-https-using-dane-dnssec IMO it's incorrectly marked as a duplicate. One question explains the problem and the expected results. The other was poorly worded and confused readers into locking it because they didn't understand it. Why are we locking both so no answers are possible?