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:11] – 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 32: | Line 33: | ||
</ | </ | ||
+ | |||
+ | |||
+ | notice this IPv4 range' | ||
+ | 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 60: | Line 65: | ||
</ | </ | ||
+ | status code on this ipv6 ranges is from another can-of-worms, | ||
+ | https:// | ||
+ | but i didnt read it. | ||
Line 262: | Line 270: | ||
+ | # some notes | ||
+ | |||
+ | ## RIPE checks dns server ip's | ||
https:// | https:// | ||
- | ionfigure | + | |
+ | configure | ||
* Make sure you set up at least two name servers that are authoritative for the zone | * Make sure you set up at least two name servers that are authoritative for the zone | ||
* Ensure that the servers are at least in different subnets, but preferably in different networks that are geographically distributed | * Ensure that the servers are at least in different subnets, but preferably in different networks that are geographically distributed | ||
+ | |||
+ | |||
+ | ## reverse lookup still lists wannes as contact; | ||
+ | |||
+ | don't know if WDS20-RIPE still reads his emails ? :-) | ||
+ | |||
+ | but changing reverse ip info needs second nameserver up & running (in a different subnet..) | ||
en/infra/ripe_db.1605438674.txt.gz · Last modified: 2020/11/15 12:11 by ptr_here