-
Notifications
You must be signed in to change notification settings - Fork 47
Open
Description
DNS resolution performed by the netclient itself is case sensitive.
One of my hosts in my network (v1.1.0, self-hosted) has a hostname starting with an uppercase letter, let's call it Host and it has been added to the test network. When registering, it created a node with the uppercase name Host. However, resolving host.test.nm.internal (lower case query) fails, while Host.test.nm.internal (upper case query) succeeds.
Similarly, if we add anotherhost to the same network, AnotherHost.test.nm.internal cannot be looked up either, only the lower-case variant of it.
As DNS names otherwise are case-insensitive, new-style DNS resolution should follow that pattern as well and perform case-insensitive comparisons.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels