in reply to Re^3: Bind zone file search
in thread Bind zone file search

I think I found the problem.

I modified your regex slightly in the beginning it starts with "/^zone..."

I found after posing this question last night that a few of the zone files have stanzas commented out.

The ^ in combination with the change to $/ seem to conflict with each other.

I think it would be easier to add a not part to the regex before zone so that what is before zone is not a comment character identifier.

Replies are listed 'Best First'.
Re^5: Bind zone file search
by Kenosis (Priest) on Sep 26, 2012 at 16:58 UTC

    Ah, good! Do you have an example of the commented-out stanzas? I suspect the regex can be modified to manage these exceptions.

      yes, most start with "//" and I have a few with "#"

      //zone "ecpt.org" { // type slave; // file "old/combined/ecpt.org"; // masters { // 204.234.17.196; // }; //};

        Try the following regex:

        /zone\s+"([^"]+)".+masters\s+{[\s#\/]*([a-zA-Z0-9.-]+)[\s#\/;]*}/s

        In addition to accommodating for the # and / characters in the zone stanzas, it handles the ; at the end of the masters' IP/domain name.

        The last character sets:

        [\s#\/]*([a-zA-Z0-9.-]+)[\s#\/;]* ^ ^ ^ | | | | | + - Character set found immediately after I +P/domain name | + - Character set allowed in IP/domain name + - Character set found immediately before IP/domain name