On 31-Aug-2007, at 0933, Chris Griffin wrote:
However 198.32.2.10 and 198.32.4.13 (ep.net DNS) are not covered by
any active prefix right now, 198.32/16 or otherwise, so that is a
bug and not a feature ;-) I am not so concerned about 198.32/16
not showing up as I am that no other prefix which will handle those
hosts is either.
A failure to reach ep.net's nameservers is presumably something to be
taken up with ep.net, though, not NANOG :-)
Looks like the failure was temporary:
route-views.oregon-ix.net>sh ip bgp regex _4555$
BGP table version is 213222472, local router ID is 198.32.162.100
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 198.32.2.0 202.249.2.86 0 7500
2497 1239 4555 i
* 207.172.6.20 5 0 6079
3356 1239 4555 i
* 209.10.12.160 0 4513 701
1239 4555 i
* 65.106.7.139 3 0 2828
1239 4555 i
(etc, etc)
Joe
