Query for newly added/modified data in zone fails at random

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Query for newly added/modified data in zone fails at random

Nikkilä, Tommi

Hi!

 

My BIND (version 9.9.4-RedHat-9.9.4-51.el7) is displaying some odd behavior. When updating a zone, BIND randomly refuses to return the newly added  and/or modified data for client. In my named.conf I have dozens of views, main interest in the following

view "nwserv" {

        include "config/zones.conf";

        match-clients {

                backup;

        };

};

 

view "CLIENT1" {

        include "config/common-slave.conf";

        include "config/CLIENT1-internal.conf";

        match-clients {

                CLIENT1;

        };

};

 

 

view "CLIENT2" {

        include "config/CLIENT2-internal.conf";

        include "config/common-slave.conf";

        max-cache-ttl 180;

        match-clients {

                CLIENT2;

        };

};

 

[...]

 

view "isfi" {

        include "config/common-slave.conf";

        match-clients {

                any;

        };

};

 

 

The "zones.conf" and "common-slave.conf" both include configurations for several zones of which the zone 207.31.172.in-addr.arpa is currently not functioning correctly. Current configuration for that zone is

zone "207.31.172.in-addr.arpa" in {

type slave;

file "slave/db.207.31.172.in-addr.arpa";

masterfile-format text;

 masters port 8054 { 192.168.100.22; };

};

 

When updating the zone, the master server transfers the zone to my slave correctly. This can be verified by viewing the corresponding db file which contains newly incremented serial and any changes made to master's db file. My problem is, however, that when querying the zone, the newly distributed changes (i.e. new serial) are at random not displayed to any clients within "nwserv" view. By doing a SIGKILL for BIND the correct behavior is restored and clients within the "nwserv" view are able to view the contents of the entire zone, including any recent changes/additions. The zones.conf includes configuration for the 207.31.172.in-addr.arpa zone and no other configuration file includes it

# grep 207.31.172.in-addr.arpa zones.conf

zone "207.31.172.in-addr.arpa" in {

file "slave/db.207.31.172.in-addr.arpa";

# grep 207.31.172.in-addr.arpa common-slave.conf

# grep 207.31.172.in-addr.arpa *.conf

zones.conf:zone "207.31.172.in-addr.arpa" in {

zones.conf: file "slave/db.207.31.172.in-addr.arpa";

 

My question is: has anyone observed similar behavior and if so, what was your solution for it?

 

Tommi Nikkilä | System Specialist

Network Services | CGI

Karvaamokuja 2, FI-00380 Helsinki | Finland

 


_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users
Reply | Threaded
Open this post in threaded view
|

Re: Query for newly added/modified data in zone fails at random

Matthew Pounsett


On 12 October 2017 at 11:03, Nikkilä, Tommi <[hidden email]> wrote:

Hi!

 

My BIND (version 9.9.4-RedHat-9.9.4-51.el7) is displaying some odd behavior. When updating a zone, BIND randomly refuses to return the newly added  and/or modified data for client. In my named.conf I have dozens of views, main interest in the following


Each view keeps its own internal state for its zones.  The way you appear to have this configured, for any zone in 'common-slave.conf' you have several versions stored (one per view) each trying to write to the same state file (e.g. slave/db.207.31.172.in-addr.arpa).  

If I were to speculate (you'd want to do some more troubleshooting to confirm), I would suspect you're running into problems with your views stomping on each other's slave files.  

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users
Reply | Threaded
Open this post in threaded view
|

Re: Query for newly added/modified data in zone fails at random

Mark Andrews

I would also upgrade from BIND 9.9 to a later version of BIND to get
the following which was introduced in BIND 9.10.0.

3673.   [func]          New "in-view" zone option allows direct sharing
                        of zones between views. [RT #32968]

Mark

In message <CAAiTEH8pDNm9shbfwfZQD=[hidden email]>

>
> On 12 October 2017 at 11:03, Nikkil=C3=A4, Tommi <[hidden email]> wr=
> ote:
>
> > Hi!
> >
> >
> >
> > My BIND (version 9.9.4-RedHat-9.9.4-51.el7) is displaying some odd
> > behavior. When updating a zone, BIND randomly refuses to return the newly
> > added  and/or modified data for client. In my named.conf I have dozens of
> > views, main interest in the following
> >
>
> Each view keeps its own internal state for its zones.  The way you appear
> to have this configured, for any zone in 'common-slave.conf' you have
> several versions stored (one per view) each trying to write to the same
> state file (e.g. slave/db.207.31.172.in-addr.arpa).
>
> If I were to speculate (you'd want to do some more troubleshooting to
> confirm), I would suspect you're running into problems with your views
> stomping on each other's slave files.
>
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: [hidden email]
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/bind-users