Skip to content

Conversation

@fogs
Copy link

@fogs fogs commented Apr 28, 2016

Although 40 labels seems high enough for most use cases (e.g. reverse resolution of a IPv6 address) our project ran into issues with a domain name with 45 labels. To avoid problems in the future, I suggest to allow for the maximum number of labels allowed for a domain name. Since the function stops immediately when a shorter DNS name is processed, this should not have any impact for other users of this library.

Although 40 labels seems high enough for most use cases (e.g. reverse resolution of a IPv6 address) our project ran into issues with a domain name with 45 labels. To avoid problems in the future, I suggest to allow for the maximum number of labels allowed for a domain name. Since the function stops immediately when a shorter DNS name is processed, this should not have any impact for other users of this library.
ansuz pushed a commit to ansuz/modern-dnsd that referenced this pull request Nov 6, 2016
Fix %pXbUQg/kZJGH13GaxApbVcAwf5iYgeZ6AglQH8FPjt8=.sha256

 jhs#5 is not completely correct or necessary so is not merged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant