Operational Status: [Status]
sslip.io 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 and uses much of the code of xip.io, which was created by Sam Stephenson.
Here are some examples:
|–1.sslip.io||::1||IPv6 — always use dashes|
sslip.io can be used to brand your own site (you don’t need to use the sslip.io domain). For example, say you own the domain “example.com”, and you want your subdomain, “xip.example.com” to have xip.io-style features. To accomplish this, you’d need to set the following four DNS servers as NS records for the subdomain “xip.example.com”
Let’s test it from the command line using
dig +short 169-254-169-254.xip.example.com @ns-gce.nono.io.
Yields, hopefully: [connection timed out]
If you have a wildcard certificate for your sslip.io-style subdomain, you may install it on your machines for TLS-verified connections.
When using a TLS wildcard certificate in conjunction with your branded sslip.io style subdomain, you must use dashes not dots as separators. For example, if you have the TLS certificate for *.xip.example.com, you could browse to https://https://52-0-56-137.xip.example.com/ but not https://184.108.40.206.xip.example.com/.
For a real-world example of a TLS wildcard cert and sslip.io domain, browse https://52-0-56-137.sslip.io.
Pivotal employees can download the *.sslip.io TLS private key here.
[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 four sslip.io nameservers. That’s normal. [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.