-
Notifications
You must be signed in to change notification settings - Fork 166
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
Units and case-sensitivity #41
Comments
Thanks for pointing this out! How about responding with all possible case combinations?
|
It seems an interesting idea. PS : the problem also arises if the resolver does 0x20 (varying the case to have more entropy, in order to fend off poisoning attempts). Knot does this by default. |
I'm having issues from my dns client evidently lowercasing queries before sending them. I might file bugs there (though it's un-/under-maintained), but it might be nice if dns.toys were robust to this. So far, I've found that units (digital) and timestamp-from-to conversions error. Unit (digital)
Please consider:
Time conversion
I'm using see
$ dog @1.1 example.com xkcd.com SOA NS TXT
dog trace snippet confirming lowercasingSee line 1 with upper-case, and log starting at line 3, with lowercased domain part RFCs: standards on DNS and case-(in)sensitivityWhile RFC (4343) titled "Domain Name System (DNS) Case Insensitivity Clarification" (Jan 2006) weighs in on this,
Perhaps based on advice for handling punycode encoding of Unicode names, per RFC 5890 (2010), this dog DNS client project chooses to lowercase the inputs, which does not seem obviously wrong on its face.
|
Some units are case-sensitive, for instance MB and Mb are different things. But the DNS is case-insensitive, which means that this behavior is logical, but surprising:
This is even worse if DNS requests go through a forwarder which downcases everything (a bad idea, but it may happen). May be a word in the documentation?
The text was updated successfully, but these errors were encountered: