Re: Intradomain DNS Anycast revisited

2005-03-30 Thread Bill Woodcock
On Fri, 25 Mar 2005, Joe Shen wrote: Do you mean Quagga's OSPF route has higher priority than static route? or even there is static default route configured, once Quagga detects link to default router is down it will replace 0.0.0.0/0.0.0.0 in host routing table?

Re: Intradomain DNS Anycast revisited

2005-03-28 Thread Bill Woodcock
I like BGP more as I could transport that /32 with no-export right away. Yes, in a simple hub-and-spoke anycast topology, iBGP is simplest. In a wagon-wheel or mesh topology, having an IGP makes some things simplest, though you can still use iBGP in that role.

Re: Intradomain DNS Anycast revisited

2005-03-28 Thread Peter John Hill
On Mar 28, 2005, at 8:40 AM, Bill Woodcock wrote: I like BGP more as I could transport that /32 with no-export right away. Yes, in a simple hub-and-spoke anycast topology, iBGP is simplest. In a wagon-wheel or mesh topology, having an IGP makes some things simplest, though you can still use

Re: Intradomain DNS Anycast revisited

2005-03-27 Thread Peter John Hill
On Mar 26, 2005, at 1:41 PM, just me wrote: 1) should each dns cache server be configured a static default route (0.0.0.0/0.0.0.0)? If server-(1,3) is configured statically to use router-1 as default router, will Quagga make it use router-2 when router-1 is not reachable? configure a

Re: Intradomain DNS Anycast revisited

2005-03-27 Thread Edward B. Dreger
PJH Date: Sun, 27 Mar 2005 08:44:34 -0800 PJH From: Peter John Hill PJH configure a loopback interface on your dns servers and advertise a PJH route to that loopback address to your connected routers... We've used this approach for several years. It works very well. Eddy -- Everquick

Re: Intradomain DNS Anycast revisited

2005-03-26 Thread Alexander Koch
On Thu, 24 March 2005 22:25:36 -0800, Bill Woodcock wrote: No, because both routers are reached through the same L1/L2 medium, so Quagga can't use link-state to determine reachability of the next-hop. You could fix that by getting rid of the switches, and just having a bunch Hmh. Thinking

MARP (was Re: Intradomain DNS Anycast revisited)

2005-03-26 Thread Mikael Abrahamsson
On Sat, 26 Mar 2005, Alexander Koch wrote: All that as less and less real routers[tm] have FE connection in them where you could work on link-state... and you need a 'dynamic' component to tell you the connection over some GE aqggregation gear is still there, and if you combine this with the

Re: Intradomain DNS Anycast revisited

2005-03-26 Thread just me
It has been my experience in the deployment of such anycasted dns server pods that pushing ospf from the dns server hosts introduces complexity and reduces reliability to the point that other, simpler solutions become much more attractive. You should also take a moment to take a look at your

Intradomain DNS Anycast revisited

2005-03-24 Thread Joe Shen
Hi, I'm trying to set up a anycast DNS server farm for customer service. In order to improve availability, we plan to install those servers in one LAN which has the similar structure like : server-(1,3)---switch1---router-1---(outside) | |

Re: Intradomain DNS Anycast revisited

2005-03-24 Thread Bill Woodcock
1) should each dns cache server be configured a static default route (0.0.0.0/0.0.0.0)? If server-(1,3) is configured statically to use router-1 as default router, will Quagga make it use router-2 when router-1 is not reachable? No, because both routers are reached

Re: Intradomain DNS Anycast revisited

2005-03-24 Thread Joe Shen
thanks. No, because both routers are reached through the same L1/L2 medium, so Quagga can't use link-state to determine reachability of the next-hop. You could fix that by getting rid of the switches, and just having a bunch of router interfaces facing two Ethernet interfaces on each