Operational Status: [Status] is a DNS (Domain Name System) service that, when queried with a hostname with an embedded IP address, returns that IP Address. It was inspired by, which was created by Sam Stephenson.

Here are some examples:

Hostname / URL IP Address Notes dot separators, website mirror (IPv4) dash separators, website mirror (IPv4) subdomain subdomain + dashes dash prefix, website mirror (IPv4) ::1 IPv6 — always use dashes, never dots 2a01:4f8:c17:b8f::2 website mirror (IPv6)

Branding / White Label / Custom Domains can be used to brand your own site (you don’t need to use the domain). For example, say you own the domain “”, and you want your subdomain, “” to have features. To accomplish this, set the following three DNS servers as NS records for the subdomain “”

hostname IP address Location
USA USA Singapore

Let’s test it from the command line using dig:

dig +short

Yields, hopefully: [connection timed out]

But I Want My Own DNS Server!

If you want to run your own DNS server, it's simple: you can compile from source or you can use one of our pre-built binaries. In the following example, we install & run our server within a docker container:

docker run -it --rm fedora
curl -L -o dns-server
chmod +x dns-server
./dns-server 2> dns-server.log &
dnf install -y bind-utils
dig @localhost +short # returns ""


You can acquire TLS certificates for your externally-accessible hosts from certificate authorities (CAs) such as Let's Encrypt. The easiest mechanism to acquire a certificate would be to use the HTTP-01 challenge. It requires, at a minimum, a web server running on your machine. The Caddy web server is one of the most popular examples. For example, if you had a webserver with the IP address, you could obtain a TLS certificate for "", or "", or "".

If you have procured a wildcard certificate for your branded / white label / custom subdomain, you may install it on your machines for TLS-verified connections.

When using a TLS wildcard certificate in conjunction with your branded style subdomain, you must use dashes not dots as separators. For example, if you have the TLS certificate for *, you could browse to but not

if you're interested in acquiring a wildcard certificate for your domain, e.g. "*", the procedure is described here.

Determining Your External IP Address via DNS Lookup

You can use's DNS servers (,, to determine your public IP address by querying the TXT record of the root domain. If you're curious about your public IPv6 address, use the DNS server, for it has both IPv4 and IPv6 addresses:

dig txt . +short    # sample reply "2607:fb90:464:ae1e:ed60:29c:884c:4b52"
dig txt . +short -4 # forces IPv4 lookup; sample reply ""
dig txt . +short -6 # forces IPv6 lookup; sample reply "2607:fb90:464:ae1e:ed60:29c:884c:4b52"

This feature was inspired by Google's DNS lookup, i.e. dig txt @ +short. There are also popular HTTP-based services for determining your public IP address:

A big advantage of using DNS queries instead of HTTP queries is bandwidth: querying requires a mere 592 bytes spread over 2 packets; Querying requires 8692 bytes spread out over 34 packets—over 14 times as much! Admittedly bandwidth usage is a bigger concern for the one hosting the service than the one using the service.


[Status] A status of “build failing” rarely means the system is failing. It’s more often an indication that when the servers were last checked (currently every six hours), the CI (continuous integration) server had difficulty reaching one of the three nameservers. That’s normal. [connection timed out]

[connection timed out]

DNS runs over UDP which has no guaranteed delivery, and it’s not uncommon for the packets to get lost in transmission. DNS clients are programmed to seamlessly query a different server when that happens. That’s why DNS, by fiat, requires at least two nameservers (for redundancy). From IETF (Internet Engineering Task Force) RFC (Request for Comment) 1034:

A given zone will be available from several name servers to insure its availability in spite of host or communication link failure. By administrative fiat, we require every zone to be available on at least two servers, and many zones have more redundancy than that.