GuidesConnect a domain
How Ferry verifies a domain
Ferry asks for a new name under the domain and makes sure that the request comes back to this server.
Ferry makes a name that nobody used before: ferry-check-<random>.example.com.
1 / 4
Ferry uses a new name each time, for two reasons. Only a wildcard DNS record can answer for a new name. And no DNS cache has an old answer for it.
The two checks
| Check | Question | It passes when |
|---|---|---|
dns | What does the name resolve to? | It resolves to the public address of the server. |
http | Who answers a request for it on the public HTTP port? | This server answers. |
For the http check, the proxy answers on a path that only this check uses. The answer is a value that only this process knows.
Verify now
Ferry tests a domain each 15 seconds. To test immediately, click Verify now, or run the command.
Terminal
$ ferry domains verify example.comexample.com reaches this server: services are served at https://<service>.example.com dns passed *.example.com resolves to 203.0.113.10, this server. http passed This server answers on port 80 for names under example.com.While the domain does not reach the server, the command stops with the exit code 1. Thus a script can wait for the domain.