Skip to content
This repository was archived by the owner on Oct 21, 2022. It is now read-only.

is base36 resolve returning an inverted IPv4 address? #5

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vmmello
Copy link

@vmmello vmmello commented Mar 11, 2017

Hi,

I've tested resolving the base36 name for the first time today, and I got the impression that it's returning an inverted IPv4 as the response.

I've tried with IP 104.131.190.237. So first I got the decimal value from it:

$ echo $(( (104 * (256**3)) + (131 * (256**2)) + (190 * 256) + 237 ))
1753464557

Converting to base36 that gives: szytwt

But when resolving it's returning the previous IP inverted:

$ ping szytwt.xip.io
PING szytwt.xip.io (237.190.131.104) 56(84) bytes of data.

Is that correct and I'm missing something very obvious? Or is it returning the IP inverted?

Thanks in advance.

base36 name resolving was converting the IPv4 address backwards. Fixed it.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant