Thank you Sir!
On Mon, Aug 13, 2012 at 8:08 PM, Mark Andrews wrote:
>
> In message
>
> , Red Cricket writes:
>> Hi,
>>
>> I am running bind 9.9.1-P1 and I have in my named.conf this zone ...
>>
>> zone "example.com" {
>> ...
>> allow-update {
>> 192.168.1.32;
>> 192.168.1.
In message
, Red Cricket writes:
> Hi,
>
> I am running bind 9.9.1-P1 and I have in my named.conf this zone ...
>
> zone "example.com" {
> ...
> allow-update {
> 192.168.1.32;
> 192.168.1.33;
> key example.com.key;
> };
> };
allow-update { !{ !192.168.1.32;
Hi,
I am running bind 9.9.1-P1 and I have in my named.conf this zone ...
zone "example.com" {
...
allow-update {
192.168.1.32;
192.168.1.33;
key example.com.key;
};
};
I was hoping that this meant that only hosts 192.168.1.32 and
192.168.1.33 with the key exam
On Mon, Aug 13, 2012 at 10:18 AM, John Williams wrote:
> I've a system with two interfaces; a management and a data interface. My
> default route is set out to the data interface.
>
> doing a
>
> dig +tcp someIP.com @some.resolver
>
> works fine.
>
> If I want a UDP based query, I have to specify
I've a system with two interfaces; a management and a data interface. My
default route is set out to the data interface.
doing a
dig +tcp someIP.com @some.resolver
works fine.
If I want a UDP based query, I have to specify -b option and provide IP of the
interface otherwise it fails.
5 matches
Mail list logo