I hate to be the bearer of bad news but . . .
DMOZ is having some real big resolution problems. In most cases your url does not resolve, your dns does not answer or your dns is not propagating it's secondaries.
During the past few months public peering has gone to the dogs. Routing issues now plague the net and this is far worse then dying dot.com plague of the past. In committee at the Brookings Institute it was discussed how the big telco's were taking back the net as the smaller telcos decay. The days of "Free" peering are gone and those that don't pay are locked out or experience an inadvertantly transit delay. What happens as the peering is lost, network adminstrators establish peering via 2nd or 3rd tier peers that may have switched to the paid peering or have other routes that can be alternately re-routed or back-hauled routes to broadcast their BGP sessions under a alternate quasi point of presence. However, these quasi back-hauled peered configurations are supported by other multi-homed OPSF BGP clients that are at the mercy of the routing updates of their now "upstream" peers. When the upstream peers recieves an update or the route flaps, a new routing table is created. If the routes change again, then yet another routing table is created. Most routers check table every 15-30 seconds and then continue routing. This condition can and has caused continuous table update loops that cause even more routes to flap which invoke even more updates thus the production of a cascading and virtually perpetual loop is formed and held until the flapping route is either isolated or the interface is cleared and/or shutdown. The result is the same a polluted routing table as experienced a year or so ago.
Sorry, I may have over babbled.
<img src="/images/icons/blush.gif" alt="" />
-Darren
DMOZ is having some real big resolution problems. In most cases your url does not resolve, your dns does not answer or your dns is not propagating it's secondaries.
During the past few months public peering has gone to the dogs. Routing issues now plague the net and this is far worse then dying dot.com plague of the past. In committee at the Brookings Institute it was discussed how the big telco's were taking back the net as the smaller telcos decay. The days of "Free" peering are gone and those that don't pay are locked out or experience an inadvertantly transit delay. What happens as the peering is lost, network adminstrators establish peering via 2nd or 3rd tier peers that may have switched to the paid peering or have other routes that can be alternately re-routed or back-hauled routes to broadcast their BGP sessions under a alternate quasi point of presence. However, these quasi back-hauled peered configurations are supported by other multi-homed OPSF BGP clients that are at the mercy of the routing updates of their now "upstream" peers. When the upstream peers recieves an update or the route flaps, a new routing table is created. If the routes change again, then yet another routing table is created. Most routers check table every 15-30 seconds and then continue routing. This condition can and has caused continuous table update loops that cause even more routes to flap which invoke even more updates thus the production of a cascading and virtually perpetual loop is formed and held until the flapping route is either isolated or the interface is cleared and/or shutdown. The result is the same a polluted routing table as experienced a year or so ago.
Sorry, I may have over babbled.
<img src="/images/icons/blush.gif" alt="" />
-Darren
