|
5 | 5 | order: 7 |
6 | 6 | --- |
7 | 7 |
|
8 | | -import { GlossaryTooltip } from "~/components"; |
| 8 | +import { Details, GlossaryTooltip } from "~/components"; |
9 | 9 |
|
10 | 10 | You must keep your <GlossaryTooltip term="Internet Routing Registry (IRR)" link="/byoip/concepts/irr-entries/">Internet Routing Registry (IRR)</GlossaryTooltip> entries up to date so that it is public information that Cloudflare has permission to advertise your prefix or prefixes, and to ensure that your traffic can be properly routed on the internet. |
11 | 11 |
|
@@ -62,47 +62,39 @@ Add or update IRR entries when they meet any of these criteria: |
62 | 62 | * The entry is incomplete or inaccurate — for example, when the route object does not show the correct origin. |
63 | 63 | * The entry is complete but requires updating — for example, when they correspond to supernets but need to correspond to subnets used in Magic Transit. |
64 | 64 |
|
65 | | -### IRR entry verification methods |
| 65 | +### Verification methods |
66 | 66 |
|
67 | | -To verify your prefix and ASN route, use the tools and methods outlined on the table below: |
| 67 | +## IRR Explorer - Subnet prefix verification |
68 | 68 |
|
69 | | -<table> |
| 69 | +Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which ASN is associated with a subnet prefix. |
70 | 70 |
|
71 | | - <thead> |
72 | | - <tr> |
73 | | - <th>Data to verify</th> |
74 | | - <th>Tool</th> |
75 | | - <th>Method</th> |
76 | | - <th>Output</th> |
77 | | - </tr> |
78 | | - </thead> |
79 | | - <tbody> |
80 | | - <tr> |
81 | | - <td>Subnet prefix IP<br/>for the ASN</td> |
82 | | - <td><a href=" https://irrexplorer.nlnog.net">IRR Explorer</a></td> |
83 | | - <td>Search for the subnet prefix IP, for example, <code>162.211.156.0/24</code>.</td> |
84 | | - <td>List of ASN numbers, source (route registry), and any associated errors.</td> |
85 | | - </tr> |
86 | | - <tr> |
87 | | - <td>ASN for the<br/>subnet prefix</td> |
88 | | - <td><span style="white-space: nowrap"><a href=" https://irrexplorer.nlnog.net">IRR Explorer</a></span></td> |
89 | | - <td><span style="white-space: nowrap">Search for the ASN, for example <code>AS13335</code>.</span></td> |
90 | | - <td><span style="white-space: nowrap">List of prefixes, source, and any associated errors.</span></td> |
91 | | - </tr> |
92 | | - <tr> |
93 | | - <td>Your origin ASN<br/>and routing data</td> |
94 | | - <td>WHOIS lookup</td> |
95 | | - <td> |
96 | | - <p>In a terminal, use this `whois` command, substituting your network prefix for <em>network-prefix</em>:</p> |
97 | | - <p>`whois -h rr.ntt.net network-prefix`</p> |
98 | | - <p>The host `rr.ntt.net` is the primary server for the Global IP network.</p> |
99 | | - </td> |
100 | | - <td>IRR route, origin, and source information.</td> |
101 | | - </tr> |
102 | | - </tbody> |
103 | | -</table> |
| 71 | +**Method:** Search for the subnet prefix IP, for example, `162.211.156.0/24`. |
104 | 72 |
|
105 | | -#### WHOIS output |
| 73 | +**Output:** List of ASN numbers, source (route registry), and any associated errors. |
| 74 | + |
| 75 | +## IRR Explorer - ASN verification |
| 76 | + |
| 77 | +Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which prefixes are associated with an ASN. |
| 78 | + |
| 79 | +**Method:** Search for the ASN, for example `AS13335`. |
| 80 | + |
| 81 | +**Output:** List of prefixes, source, and any associated errors. |
| 82 | + |
| 83 | +## WHOIS lookup |
| 84 | + |
| 85 | +Use WHOIS lookup to verify your origin ASN and routing data. |
| 86 | + |
| 87 | +**Method:** In a terminal, use this `whois` command, substituting your network prefix for *network-prefix*: |
| 88 | + |
| 89 | +```sh |
| 90 | +whois -h rr.ntt.net network-prefix |
| 91 | +``` |
| 92 | + |
| 93 | +The host `rr.ntt.net` is the primary server for the Global IP network. |
| 94 | + |
| 95 | +**Output:** IRR route, origin, and source information. |
| 96 | + |
| 97 | +<Details header="WHOIS output example"> |
106 | 98 |
|
107 | 99 | The `<IRR entry section>` in the WHOIS output shows the correct IRR entry information for the specified network. In this example, the network prefix is `1.1.1.0/24`, and the output includes the route, origin ASN, and route registry, which in this example is APNIC: |
108 | 100 |
|
@@ -135,3 +127,5 @@ source: APNIC |
135 | 127 | WHOIS output also shows the RPKI entry information for prefix IP addresses. When your WHOIS output only contains an RPKI entry, you must add the IRR entry. |
136 | 128 |
|
137 | 129 | ::: |
| 130 | + |
| 131 | +</Details> |
0 commit comments