Appreciate your help. That works.
Zhe
On 2018年09月07日 01:17, Sten Carlsen wrote:
> In the end I had to look in the BIND ARM.
>
> As I read this, the solution should be:
> options {
> listen-on { ! 10.0.1.1; any;};
> };
> The first part tells bind to not listen to 10.0.1.1 and the second part tells
In the end I had to look in the BIND ARM.
As I read this, the solution should be:
options {
listen-on { ! 10.0.1.1; any;};
};
The first part tells bind to not listen to 10.0.1.1 and the second part
tells bind to listen on any other address.
Having the Listen-on statement removes the default list
On 2018年09月06日 21:06, Sten Carlsen wrote:
>
>
> On 06/09/2018 14.33, He Zhe wrote:
>> On 2018年09月06日 20:26, Sten Carlsen wrote:
>>> On 06/09/2018 12.36, He Zhe wrote:
Hi,
How can I config to let named NOT listen on specific interfaces? Any
negation config in options like belo
On 06/09/2018 14.33, He Zhe wrote:
>
> On 2018年09月06日 20:26, Sten Carlsen wrote:
>>
>> On 06/09/2018 12.36, He Zhe wrote:
>>> Hi,
>>>
>>> How can I config to let named NOT listen on specific interfaces? Any
>>> negation config in options like below? Currently it listens on all
>>> interfaces an
On 2018年09月06日 20:26, Sten Carlsen wrote:
>
>
> On 06/09/2018 12.36, He Zhe wrote:
>> Hi,
>>
>> How can I config to let named NOT listen on specific interfaces? Any
>> negation config in options like below? Currently it listens on all
>> interfaces and compete with other DNS daemons in the same
On 06/09/2018 12.36, He Zhe wrote:
> Hi,
>
> How can I config to let named NOT listen on specific interfaces? Any negation
> config in options like below? Currently it listens on all interfaces and
> compete with other DNS daemons in the same system.
>
> options {
> listen-on { ! 10.0.1.1; };
>
6 matches
Mail list logo
