Skip to content
This repository was archived by the owner on Jun 2, 2020. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions content/guides/examples/websites.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,13 +119,16 @@ you plan to use, you can find it using the command like:
```bash
$ nslookup gateway.ipfs.io
```
And noting the IPv4 addresses returned. You should create an A record for each address.
1. Note the IP addresses returned.
1. Create an A record for each IPv4 address (all results that look like 192.0.2.71).
Comment thread
jessicaschilling marked this conversation as resolved.
1. Create an AAAA record for each IPv6 address (all results that look like 2001:DB8:324A::A1).
Comment thread
jessicaschilling marked this conversation as resolved.
1. Periodically check if one of these addresses changed and update the record.
Comment thread
jessicaschilling marked this conversation as resolved.

Visitors' browsers will send `your.domain` in the Host header of their requests.
The ipfs gateway will recognize `your.domain`, look up the value of the DNS TXT for your domain,
then serve the files in `/ipns/your.domain/` instead of `/`.

If you point `your.domain`'s A record to the IPv4 addreses of `gateway.ipfs.io`, and
If you point `your.domain`'s A and AAAA record to the IP addreses of `gateway.ipfs.io`, and
then wait for the DNS to propagate, then anyone should be able to access your
ipfs-hosted site without any extra configuration at `http://your.domain`.

Expand Down