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
After supporting RFC1123 the limit of 63 chars is default, but when an underscore is prefixed for some records (e.g., port SRV records) they then can become too long and fail to query. It appears any time an underscore is prefixed the name length must be potentially truncated back to 63 chars.
For example, this would be a valid length of 63 chars without the underscore:
# dig _port0._longapplicationname-1234567890123456789012345678901234567890123._tcp.marathon.mesos
dig: '_longapplicationname-1234567890123456789012345678901234567890123._tcp.marathon.mesos' is not a legal name (label too long)
The text was updated successfully, but these errors were encountered:
After supporting RFC1123 the limit of 63 chars is default, but when an underscore is prefixed for some records (e.g., port SRV records) they then can become too long and fail to query. It appears any time an underscore is prefixed the name length must be potentially truncated back to 63 chars.
For example, this would be a valid length of 63 chars without the underscore:
But this fails:
The text was updated successfully, but these errors were encountered: