2011/9/26 Matus UHLAR - fantomas :
>> 2011/9/23 Kevin Darcy :
>>>
>>> NXDOMAIN is a *permanent* response; at least it's "permanent" in the
>>> absence
>>> of any change the relevant DNS RRset or zone.
>>>
>>> You're almost certainly getting the NXDOMAIN because you're spoofing the
>>> root servers,
2011/9/23 Kevin Darcy :
NXDOMAIN is a *permanent* response; at least it's "permanent" in the absence
of any change the relevant DNS RRset or zone.
You're almost certainly getting the NXDOMAIN because you're spoofing the
root servers, and your "fake" root servers don't have the same knowledge as
2011/9/23 Kevin Darcy:
You're almost certainly getting the NXDOMAIN because you're spoofing
the
root servers, and your "fake" root servers don't have the same
knowledge as
the real ones, so they'll return NXDOMAIN for some queries (whereas
dig
+trace does not, because it follows the hierarch
On 9/22/2011 8:49 PM, Drunkard Zhang wrote:
2011/9/23 Kevin Darcy:
On 9/21/2011 10:01 PM, Drunkard Zhang wrote:
Why are you going through all of these gyrations? The forwarding
algorithm
in BIND has for a long time been based on RTT, so if one forwarder, or a
set
of forwarders, stops working, t
2011/9/23 Kevin Darcy :
> On 9/21/2011 10:01 PM, Drunkard Zhang wrote:
>>>
>>> Why are you going through all of these gyrations? The forwarding
>>> algorithm
>>> in BIND has for a long time been based on RTT, so if one forwarder, or a
>>> set
>>> of forwarders, stops working, the other(s) will be u
On 9/22/2011 6:03 AM, Drunkard Zhang wrote:
Oops, I misunderstood. But I want to resolve this problem: take
news.qq.com for example, I DID saw that it's unresolvable to one group
(they returned NXDomain), at meantime it's no problem to another
group, and "dig news.qq.com +trace" returned correct
On 9/21/2011 10:01 PM, Drunkard Zhang wrote:
Why are you going through all of these gyrations? The forwarding algorithm
in BIND has for a long time been based on RTT, so if one forwarder, or a set
of forwarders, stops working, the other(s) will be used automatically. In
other words, forwarder fai
>> Oops, I misunderstood. But I want to resolve this problem: take
>> news.qq.com for example, I DID saw that it's unresolvable to one group
>> (they returned NXDomain), at meantime it's no problem to another
>> group, and "dig news.qq.com +trace" returned correct answer on both
>> group. It seems
Why are you going through all of these gyrations? The forwarding algorithm
in BIND has for a long time been based on RTT, so if one forwarder, or a set
of forwarders, stops working, the other(s) will be used automatically. In
other words, forwarder failover works without any special configuration.
> Why are you going through all of these gyrations? The forwarding algorithm
> in BIND has for a long time been based on RTT, so if one forwarder, or a set
> of forwarders, stops working, the other(s) will be used automatically. In
> other words, forwarder failover works without any special configu
>> When I query a name, the dns-cache queries forwarders for gTLDs
>> instead of using local hint file, why?
>
> local "hint" file? I'm not sure what you mean here.
This file just replace the original root-servers with all my 4
recursive DNS's domain name and IP, nothing other.
>>
>> And the dns-
On 9/21/2011 7:33 AM, Drunkard Zhang wrote:
2011/9/20 Drunkard Zhang:
I got 4 DNSs doing recursive resolution, which splited into 2 groups,
and a couple of dns caches. Each group of recursion DNS using their
own net link, which is different.
Here's problem: I want a dns-cache to use one group o
On 9/20/2011 5:08 AM, Drunkard Zhang wrote:
I got 4 DNSs doing recursive resolution, which splited into 2 groups,
and a couple of dns caches. Each group of recursion DNS using their
own net link, which is different.
Here's problem: I want a dns-cache to use one group of recursion DNS
as their
2011/9/20 Drunkard Zhang :
I got 4 DNSs doing recursive resolution, which splited into 2 groups,
and a couple of dns caches. Each group of recursion DNS using their
own net link, which is different.
Here's problem: I want a dns-cache to use one group of recursion DNS
as their forwarders, and use
2011/9/20 Drunkard Zhang :
> I got 4 DNSs doing recursive resolution, which splited into 2 groups,
> and a couple of dns caches. Each group of recursion DNS using their
> own net link, which is different.
>
> Here's problem: I want a dns-cache to use one group of recursion DNS
> as their forwarders
I got 4 DNSs doing recursive resolution, which splited into 2 groups,
and a couple of dns caches. Each group of recursion DNS using their
own net link, which is different.
Here's problem: I want a dns-cache to use one group of recursion DNS
as their forwarders, and use another group as backup. ( I
16 matches
Mail list logo
