Skip to content

Commit 91a0540

Browse files
Remove extra h3, correct h-level, and move note outside Details
1 parent dbfda60 commit 91a0540

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

src/content/docs/byoip/concepts/irr-entries/best-practices.mdx

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -62,25 +62,23 @@ Add or update IRR entries when they meet any of these criteria:
6262
* The entry is incomplete or inaccurate — for example, when the route object does not show the correct origin.
6363
* The entry is complete but requires updating — for example, when they correspond to supernets but need to correspond to subnets used in Magic Transit.
6464

65-
### Verification methods
66-
67-
## IRR Explorer - Subnet prefix verification
65+
### Subnet prefix verification
6866

6967
Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which ASN is associated with a subnet prefix.
7068

7169
**Method:** Search for the subnet prefix IP, for example, `162.211.156.0/24`.
7270

7371
**Output:** List of ASN numbers, source (route registry), and any associated errors.
7472

75-
## IRR Explorer - ASN verification
73+
### ASN verification
7674

7775
Use [IRR Explorer](https://irrexplorer.nlnog.net) to verify which prefixes are associated with an ASN.
7876

7977
**Method:** Search for the ASN, for example `AS13335`.
8078

8179
**Output:** List of prefixes, source, and any associated errors.
8280

83-
## WHOIS lookup
81+
### WHOIS lookup
8482

8583
Use WHOIS lookup to verify your origin ASN and routing data.
8684

@@ -122,10 +120,10 @@ last-modified: 2018-03-16T16:58:06Z
122120
source: APNIC
123121
```
124122

123+
</Details>
124+
125125
:::note
126126

127127
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.
128128

129-
:::
130-
131-
</Details>
129+
:::

0 commit comments

Comments
 (0)