Then the load balancer should return default records or 0.0.0.0/:: to
indicate the name is good but doesn't currently have a address.
I like that solution, actually. Even if the client doesn't recognize
it
as a special address, hopefully if it tries to connect to it, the
packet won't make it
On 3/1/2011 5:27 PM, Kevin Darcy wrote:
See my other post. This is designed-in behavior for Cisco GSSes, since
there is no service unavailable, try again later RCODE.
- Kevin
When the question is what is the ip address of 'foo' an answer of the
web server is down in nonsensical.
--
Dave
On Mar 1, 2011, at 5:27 PM, Kevin Darcy wrote:
See my other post. This is designed-in behavior for Cisco GSSes,
since there is no service unavailable, try again later RCODE.
Yes[0].
W
[0]: there is no service unavailable, try again later RCODE.
On 3/2/2011 10:34 AM, David Sparro wrote:
On 3/1/2011 5:27 PM, Kevin Darcy wrote:
See my other post. This is designed-in behavior for Cisco GSSes, since
there is no service unavailable, try again later RCODE.
When the question is what is the ip address of 'foo' an answer of
the web server
with unresolvable domain (subdomain, actually)
In message 4d6d7268.1080...@chrysler.com, Kevin Darcy writes:
I got a trouble ticket on this too.
From the looks of things, Cisco is using GSSes to load-balance this
site. GSSes return SERVFAIL if all of the resources behind the
load
On 3/2/2011 1:20 PM, Kevin Darcy wrote:
I'm not saying I agree with this perspective, only that I've dealt with
load-balancer vendors enough (Cisco in particular) to understand that
this is where they're coming from.
Besides, what alternative is there? If the load-balancer returns an
address
On Mar 2, 2011, at 1:20 PM, Kevin Darcy wrote:
On 3/2/2011 10:34 AM, David Sparro wrote:
On 3/1/2011 5:27 PM, Kevin Darcy wrote:
See my other post. This is designed-in behavior for Cisco GSSes,
since
there is no service unavailable, try again later RCODE.
When the question is what is
On 3/1/2011 6:30 PM, Mark Andrews wrote:
In message4d6d7268.1080...@chrysler.com, Kevin Darcy writes:
I got a trouble ticket on this too.
From the looks of things, Cisco is using GSSes to load-balance this
site. GSSes return SERVFAIL if all of the resources behind the
load-balancer are down
A few options:
1: once the LB knows that all back-ends are down, it can continue to answer
with the correct A, but drop the TTL to be much shorter -- this allows
things to recover faster.
This would work well because the actually web site wasn't down, at least not
yesterday. If I substituted the
01, 2011 3:31 PM
To: Kevin Darcy
Cc: bind-us...@isc.org
Subject: Re: Help with unresolvable domain (subdomain, actually)
In message 4d6d7268.1080...@chrysler.com, Kevin Darcy writes:
I got a trouble ticket on this too.
From the looks of things, Cisco is using GSSes to load-balance this
site
-
From: Mike Bernhardt [mailto:bernha...@bart.gov]
Sent: Tuesday, March 01, 2011 12:40 PM
To: bind-users@lists.isc.org
Subject: Help with unresolvable domain (subdomain, actually)
For some reason, we can no longer resolve tools.cisco.com. there are several
clues to the problem but I can't put them
See my other post. This is designed-in behavior for Cisco GSSes, since
there is no service unavailable, try again later RCODE.
In message 4d6d7268.1080...@chrysler.com, Kevin Darcy writes:
I got a trouble ticket on this too.
From the looks of things, Cisco is using GSSes to load-balance this
site. GSSes return SERVFAIL if all of the resources behind the
load-balancer are down (which it determines via a heartbeat
13 matches
Mail list logo
