Quote:
Originally Posted by lazydog
Have you checked you logs for any startup errors? How about using the named-checkconf and named-checkzone to check your configurations?
|
Named-checkconf and named-checkzone find no errors. I do have this show up in /var/log/messages for errors when I try to do a DIG on the external zone brsbld.ihost.com
Apr 17 09:32:31 bbridns01 named[1717]: client 10.101.8.2#55756: view Internal: transfer of 'bldbcrs.net/IN': AXFR started
Apr 17 09:32:31 bbridns01 named[1717]: client 10.101.8.2#55756: view Internal: transfer of 'bldbcrs.net/IN': AXFR started
Apr 17 09:32:31 bbridns01 named[1717]: client 10.101.8.2#55756: view Internal: transfer of 'bldbcrs.net/IN': AXFR ended
Apr 17 09:32:31 bbridns01 named[1717]: client 10.101.8.2#55756: view Internal: transfer of 'bldbcrs.net/IN': AXFR ended
Apr 17 09:32:56 bbridns01 named[1717]: client 129.42.206.11#41783: view Internal: bad zone transfer request: 'brsbld.ihost.com/IN': non-authoritative zone (NOTAUTH)
Apr 17 09:32:56 bbridns01 named[1717]: client 129.42.206.11#41783: view Internal: bad zone transfer request: 'brsbld.ihost.com/IN': non-authoritative zone (NOTAUTH)
---------- Post added 04-18-15 at 05:41 AM ----------
He guys just wanted to update this to let you know what I found out for the solution. Under my Internal view the match-clients argument was messing me up.
match-clients { internal_hosts; !external_slave; internal_slave; };
The internal_hosts acl includes the range 129.42.0.0/16. This was listed before the !external_slave; argument so it was picking that up first because the slave server is 129.42.206.11 and putting it into the internal view. I rearranged it so that it excludes the external_slave first then it was properly being picked up by the external view.
match-clients { !external_slave; internal_hosts; internal_slave; };[COLOR="Silver"]