Split DNS(view configuration)

2014-05-19 Thread Techs_Maru
Hi, There is a question though "Split DNS(view configuration)" is used. In the case of the structure such as the following, --- --- The zone is forwarded only to "View internal" because it matches it internal. I want to forward hoge.zone of BIND1

Re: Split DNS(view configuration)

2014-05-19 Thread Techs_Maru
Sorry,The description was forgotten. BIND1 is Master, and BIND2 is Slave. There is a restriction that cannot make zone of BIND2 Master by manually. 2014-05-19 20:44 GMT+09:00 Techs_Maru : > Hi, > > There is a question though "Split DNS(view configuration)" is used. > In the case of the structure

Re: Split DNS(view configuration)

2014-05-19 Thread Tony Finch
Techs_Maru wrote: > > The zone is forwarded only to "View internal" because it matches it > > internal. > > I want to forward hoge.zone of BIND1 to both hoge.zone that uses View > > configuration of BIND2. I am not sure if I understand exactly what you want. A common way to choose what view t

Re: Split DNS(view configuration)

2014-05-19 Thread Techs_Maru
Thank you for reply. I am sorry that I cannot explain that well. is master(Example IP:AAA.AAA.AAA.AAA) config. zone "hoge.com" IN { type master; file "hoge.zone"; notify yes; also-notify {

Re: Split DNS(view configuration)

2014-05-19 Thread Tony Finch
Techs_Maru wrote: > > view"internal" { > recursion yes; > zone "." IN { ... }; I think it is better to use named's built-in root hints, so you don't need to explicitly configure this. > zone "hoge.com" IN { > type slave; > masters { AA

Default BIND query timeouts

2014-05-19 Thread Shawn Zhou
I  am looking at some scripts that use IO::Socket::INET and IO::Select for testing BIND. UDP sockets are created use use IO::Socket::INET and sockets are polled via IO::Select at 6-second interval. my  $sock = IO::Socket::INET->new(     PeerHost => $server,     PeerPort =

Re: Default BIND query timeouts

2014-05-19 Thread Kevin Darcy
If a client sends a recursive query to the BIND instance, and that instance needs to fetch the answer from one or more other upstream sources, then my understanding is that the "resolver-query-timeout" global option (see the BIND docs) controls the timeout for each one of those upstream transac

Re: Default BIND query timeouts

2014-05-19 Thread Shawn Zhou
What about non-recursive queries? In particular case, our test queries are non-recursive and we expect the name server should have answers. We are sending test host with very high query rate so BIND may be too busy to respond to all the queries. On Monday, May 19, 2014 4:25 PM, Kevin Darcy