en:infra:ripe_db
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:infra:ripe_db [2020/11/15 12:25] – ptr_here | en:infra:ripe_db [2022/07/22 13:15] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | some info i collected from RIPE database (the european ip number authority) | + | some info collected from RIPE database (the european ip number authority) |
+ | database data shown is in ' | ||
# IP ranges | # IP ranges | ||
Line 34: | Line 35: | ||
- | notice this IPv4 range is ' | + | notice this IPv4 range's ' |
which is an important detail for the operation of a shared datacenter, as neutrinet cannot specify an abuse-contact to a specific ip address (or range of ip-addresses) | which is an important detail for the operation of a shared datacenter, as neutrinet cannot specify an abuse-contact to a specific ip address (or range of ip-addresses) | ||
Line 64: | Line 65: | ||
</ | </ | ||
+ | status code on this ipv6 ranges is from another can-of-worms, | ||
+ | https:// | ||
+ | but i didnt read it. | ||
Line 282: | Line 286: | ||
don't know if WDS20-RIPE still reads his emails ? :-) | don't know if WDS20-RIPE still reads his emails ? :-) | ||
- | WDS20-RIPE is still used; but changing reverse ip info needs second nameserver up & running (in a different subnet..) | + | but changing reverse ip info needs second nameserver up & running (in a different subnet..) |
en/infra/ripe_db.1605439557.txt.gz · Last modified: 2020/11/15 12:25 by ptr_here