[nsp] intra-domain anycast

[Brian Apley]

Our DNS servers advertise /32s via RIP to their connected routers. The
routers then redistribute this into our core IGP. The A.D. is manipulated so
that RIP is preferred (otherwise, the connected routers will not
redistribute because it will see a better route via the IGP instead of RIP).
We're hoping to implement the IGP directly on the DNS platform in the
future, as well as add some scripting so that if BIND fails-unlikely-the OS
will cease to advertise the /32.

----- Original Message ----- 
From: "Haesu" <haesu at towardex.com>
To: <cisco-nsp at puck.nether.net>
Sent: Tuesday, October 21, 2003 1:03 PM
Subject: [nsp] intra-domain anycast


> Hey all,
>
> Wondering about what you guys may think...
>
> We currently have an anycast dns server prefix (65.124.20.8/29) sitting at
three different POPs.
> Basically... each dns server has IBGP peering with services router at each
POP, announcing /29 tagged with 27552:9966 (which is equivalent to
no-export).
>
> Now my question is..
> For those who do anycast within your AS, do you use IGP such as OSPF to do
it (this *seems* like the popular way), or do you just throw it on IBGP? I
have tendancy to carry only infrastructure (router next-hop addresses) on
IGP and carry everything else over ibgp (i.e. transit routes, etc. anything
need not be announced to internet are tagged no-export and other measures)..
>
> Thanks for comments/ideas :)
> -hc
>
> -- 
> Haesu C.
> TowardEX Technologies, Inc.
> Consulting, colocation, web hosting, network design and implementation
> http://www.towardex.com | haesu at towardex.com
> Cell: (978)394-2867     | Office: (978)263-3399 Ext. 170
> Fax: (978)263-0033      | POC: HAESU-ARIN
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/