I am logged in with an email address, password, MFA, and a full administrator, and I am still not able to generate an API key.   There's an option in the Organization settings way at the bottom to enable the API Generation. No one can do it until that's saved! ... View more

Thanks Philip.   The info on the cached page I posted a link too makes it sound possible with this option.   My understanding is that when the DNS server saw the Option 81 data in the packets, it would see it and add it to the database. I could be wrong, I have been once before I think! 😉 ... View more

No matter what you actually format the value in... I don't know if I even have the correct value.   From a cached google page I was able to find something, but I don't know if it's right. I tried doing a packed capture, but I get no dhcp or dns results to the dns server ip.   IF the value I need is "23" the MX doesn't seem to care how it's typed. ALL of these examples equal the same. If you have any 2 of these in there, it gives an error that it's a duplicate:     ... View more

That doesn't really help. If you look up any of the documentation, it's boggling:   The format of the Client FQDN option is: Code Len Flags RCODE1 RCODE2 Domain Name +------+------+------+------+------+------+-- | 81 | n | | | | ... +------+------+------+------+------+------+-- The above figure follows the conventions of [12]. 2.1. The Flags Field The format of the 1-octet Flags field is: 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ | MBZ |N|E|O|S| +-+-+-+-+-+-+-+-+ Wireshark shows hex values similar to these, Microsoft used DWORD values. I'm lost on this one.  ... View more