I'm just trying to figure out which intelligent human I can talk to, to get
this sorted out. The original request to GoDaddy as the registrar was to
update stale domain administrative data to resolve a technical issue, which
is failing at this time, since they claim a registrar hold, whatever that
Separate from the goodness that is RFC 9234,
Regarding the comment "HE intentionally propagates some peer routes to
other peers", in all such cases involving Hurricane Electric, one side
or the other is configured as a customer and is receiving some form of
IP Transit from Hurricane Electric.
Hurricane Electric now supports "Never via route servers" (the peeringdb
flag) as part of our route filtering algorithm.
Using peeringdb, an ASN may indicate that its routes should never be
learned via route servers.
As a simple detection method, currently route servers are detected at
run t
Hurricane Electric now uses ASPA to do hop by hop checking of AS paths
when deciding which routes to accept when building prefix filters.
Here is an example of a route failing the ASPA check.
44.31.69.0/24,rejected,AS path 4635 9002 945 7480 38254 38254 38254
38254 38254 ASPA record exists for
4 matches
Mail list logo
