Romgo wrote on 12/10/2012 06:36:10 AM:
> I had 2 old zone with forwarders configured, the forwarders was down.
> One equipment was still using one of this zone, so bind wasn't able
> to contact the forwarders and fall back to root zone.
>
> I don't really why it try the root zone but since I de
;." ?
>>>
>>>
>>>
>>>
>>> On 8 December 2012 00:26, Leonard Mills wrote:
>>>
>>>>
>>>> Which zone(s) have that forward clause? To do what I think you want to
>>>> do, the zone should be the root (dot and only
t;
>>
>>
>>
>> On 8 December 2012 00:26, Leonard Mills wrote:
>>
>>>
>>> Which zone(s) have that forward clause? To do what I think you want to
>>> do, the zone should be the root (dot and only the dot in the zone name)
>>>
>>
n-local lookups.
>> Forwarding "." will send all non-local traffic to your edge daemon.
>>
>> Len
>>
>> --
>> *From:* Romgo
>> *To:* bind-users@lists.isc.org
>> *Sent:* Friday, December 7, 2012 9:05 AM
>
Yes that was my first idea by reading the documentation.
But has my configuration is clearly using forward only, I don't understand.
Could this be a bug ?
On 7 December 2012 18:10, Ben Croswell wrote:
> It is probably related to forward first versus forward only. Forward first
> is default b
It is probably related to forward first versus forward only. Forward first
is default but will fall back to no forwarding if the forwarders fail.
On Dec 7, 2012 12:06 PM, "Romgo" wrote:
> Hello,
>
> I am currently running two bind9 server on Debian Squeeze.
> 1:9.7.3.dfsg-1~squeeze8
>
> Server 1
Hello,
I am currently running two bind9 server on Debian Squeeze.
1:9.7.3.dfsg-1~squeeze8
Server 1 is internal dns server and serve some local zone. This server
should forward all unknown requests to our public DNS server. So I
configured this server as follow :
/etc/bind/named.conf.options
7 matches
Mail list logo
