view based for particular zone only

Hi, I would like to enable view based for only few particular hosts. Is there any to to match zone name i.e domain name (not match-destination cause ip of webserver is same for all zone). With Regards Nabin Limbu ___ bind-users mailing list bind-use

Re: view based for particular zone only

At https://www.isc.org/software/bind/documentation/arm95#view_statement_grammar you can see that you can specify the clients that get a certain view Hope this helps. Regards, Serge Fonville On Fri, Dec 5, 2008 at 10:35 AM, Nabin Limbu <[EMAIL PROTECTED]> wrote: > Hi, > > I would like to enabl

Re: socket: too many open file descriptors

On 4 dic, 19:43, Mark Andrews <[EMAIL PROTECTED]> wrote: > In message <[EMAIL PROTECTED]>, > > > >  pollex writes: > > On 4 dic, 10:59, Mark Andrews <[EMAIL PROTECTED]> wrote: > > > =A0 =A0 =A0 =A0 --enable-threads=3Dyes > > > > In message <[EMAIL PROTECTED] > > com>, > > > > pollex writes: > > > >

Re: how to archieve this?

Have you considered dynamically regenerating view definitions based on your rules? If the results of your rules are stable for minutes at a time, it may work. Regards, Chris. 2008/12/5 Ken DBA <[EMAIL PROTECTED]> > > > > --- On Fri, 12/5/08, Kevin Darcy <[EMAIL PROTECTED]> wrote: > > > From: K

Re: how to archieve this?

No reason to spend that type of cash for SLB DNS. I would suggest Foundry SIXL for 1/4 of the cost http://www.foundrynet.com/products/app-switch/fixed-systems/si-xl.html No, I don't work for Foundry. - Original Message From: Ken DBA <[EMAIL PROTECTED]> To: bind-users ; Kevin Darcy <[E

Re: socket: too many open file descriptors

Are you sure the named you build was invoked? What if you directly start the named executable by hand? For example, what's the result of this? (go down to the source directory where you built bind) # cd bin/named # ./named -g # ./named -g -u bind -n 8 -t /var/lib/named -c /etc/bind/named.conf -

Oddities in my named.log. Can you explain?

Hi Everyone, I see some oddities frequently showing up in our BIND logfiles. This is on the official primary NS for our domain. *Oddity_type#1* ... view external-in: query: server.EXAMPLE.COM IN SOA -E Please note that the only thing I changed here is the domain name. I did not capitalize it, t

Re: Oddities in my named.log. Can you explain?

Keve Nagy wrote: Hi Everyone, I see some oddities frequently showing up in our BIND logfiles. This is on the official primary NS for our domain. *Oddity_type#1* ... view external-in: query: server.EXAMPLE.COM IN SOA -E Please note that the only thing I changed here is the domain name. I did no

Re: Oddities in my named.log. Can you explain?

There is a windows box configured to use your domain name and it is trying to lookup/update the active directory configuration. Send a "Cease and Desist" letter stating that you are the registered owner of the domain name in question and they should

Re: Oddities in my named.log. Can you explain?

Looks to me like someone took their laptop home that is configured for your active directory domain and the laptop is trying to call home. I use to see that all the time. I'm guessing that your AD domain and the domain that they are querying are the same? On Fri, Dec 5, 2008 at 1:17 PM, Keve Nagy

Re: Oddities in my named.log. Can you explain?

[Note: this is really off-topic for bind-users...] Somebody stood up a Windows 2003 (or earlier) Active Directory domain controller, probably outside of your firewall since it's matching on your external view, gave it a system name of "server" and created a new Active Directory domain called "EXAM