Wrong parsing result for TXT records containing semicolons

[sergiomonteleone]

The function removeComments() in parseZoneFile.js will remove any string starting with semicolon (;). Unfortunately this causes issues with TXT records with semicolon characters in it, breaking parsing.
Replacing the regular expression in removeConnets() to something like this: /^;.*/gm solves the problem.

[elgs]

Thank you so much for the PR and reminding me about the bug. I really appreciate. But the changes in this PR are too big for me to comprehend. I will try to fix the bug itself. Thank you!

[sergiomonteleone]

Hi and thanks for your quick reply.
I'm sorry, I selected the wrong branch while submitting the PR and created this huge PR mess... my bad.

I just wanted to propose a simple modification, which changes the regular expression used in the function removeComments()

Here is a link to the patch I used in my working copy: https://gist.github.com/sergiomonteleone/a3fc44c2c6f8ca6b54f057ac3b3fa72e

Note: while this will prevent the parser from removing characters from the TXT records, it may fail to remove inline comments, as this regex will only select lines starting with semicolon. TLDR it may need more testing.