You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, a rather nasty issue with windows clients: Some of them query WINDOMAIN.LOCAL – upper case.
Which dnrd doesn't match against "-s 169.254.0.53:windowmain.local".
Adding the same upper case doesn't work either.
This badly breaks real world ActiveDirectory clients.
Will have a look to fix myself, but skills and tthe resulting time needed scare me...
For the records:
This very poor and uninvestigated diff solves my problem for now:
--- domnode.c 2004-10-19 13:45:21.000000000 +0000
+++ /tmp/domnode.c 2019-06-11 18:58:34.736213000 +0000
@@ -157,7 +157,7 @@
will be encoded as "\3yes\3org" while hayes.org will be encoded
as "\5hayes\3org"
*/
Hello, a rather nasty issue with windows clients: Some of them query WINDOMAIN.LOCAL – upper case.
Which dnrd doesn't match against "-s 169.254.0.53:windowmain.local".
Adding the same upper case doesn't work either.
This badly breaks real world ActiveDirectory clients.
Will have a look to fix myself, but skills and tthe resulting time needed scare me...
And there's another ugly thing to cope with:
Some cisco phones require case sensitive answers: https://drjohnstechtalk.com/blog/2015/04/example-of-case-sensitive-dns-usage/
Don't know if that would work with current code... (assuming upstream DNS responds case sensitive).
Thanks,
-harry
The text was updated successfully, but these errors were encountered: