Forum Discussion
I can't connect to Azure ATP with a Domain Name with numbers as a domain
ipcdollar1 , Taking back what I wrote before, you are correct. While the code declares it enforces the RFC, it's clearly a bug that it allowed first character as digit in the label.
I will add it to the internal ticket. Product will have to decide if they want to continue to stick to the RFC, in which case fix it to not allow, or change the rules to align with AD rules, which might make more sense here.
Thanks for the feedback!
But you allow this for example:
nb.1we2.contoso.org
Why?
If you are not compliant to RFC 1035, why not allow numeric only host/domain name?
Microsoftipcdollar1 , Taking back what I wrote before, you are correct. While the code declares it enforces the RFC, it's clearly a bug that it allowed first character as digit in the label.
I will add it to the internal ticket. Product will have to decide if they want to continue to stick to the RFC, in which case fix it to not allow, or change the rules to align with AD rules, which might make more sense here.
Thanks for the feedback!
- Hi All,
I have the same issue with an ADDS domain name that has underscore (is not DNS RFC compliant) but ADDS allowed it.
When do you think that this can be solved (alignment between MD4I sensor config and ADDS domain allowed naming syntax)?
