or, in bind options : empty-zones-enable yes;
any server running bind not understanding this should result is two
things
1: the responsible admins resignation
2: ensuring his/her replacement upgrades to something modern.
On 16/02/2014 07:43, li...@rhsoft.net wrote:
> Am 15.02.2014 22:37, schrieb SW:
>
>> Yes, you are correct. That is the cause of the problem. A quick entry of my
>> machine in the hosts file sorted that one out! I'm just baffled why I have
>> never experienced this issue before
_______________________________________________________________________________
zone "1.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "2.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
zone "3.10.IN-ADDR.ARPA" {
type master;
file "named.empty";
};
<big snip>
