Cookies Disclaimer

I agree Our site saves small pieces of text information (cookies) on your device in order to authenticate logins, deliver better content and provide statistical analysis. You can adjust your browser settings to prevent our site from using cookies, but doing so will prevent some aspects of the site from functioning properly.

Server IP?

eqsasukei
Is there an IP address released for the server? I am having connection issues and I think there is a bad hop between me and the server due to the winter storm moving in but I want to make sure.

Thanks.
Ryan Dancey
There are systems between us and you that change IP addresses so there is no single IP that the server is on. If you can traceroute to pfo.goblinworks.com you can see the current path.
crodnj2012
Tracing route to pfo.goblinworks.com [66.113.104.101]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 39 ms 16 ms 36 ms cpe-76-178-96-1.natsow.res.rr.com [76.178.96.1]

3 13 ms 12 ms 11 ms tge7-1.yumaaz1401h.socal.rr.com [76.166.6.73]
4 16 ms 12 ms 11 ms tge2-1.yumaaz1401r.socal.rr.com [72.129.49.192]

5 22 ms 23 ms 18 ms tge2-14-0-11.lsancarc01r.socal.rr.com [72.129.49
.24]
6 22 ms 23 ms 19 ms bu-ether36.lsancarc0yw-bcr00.tbone.rr.com [107.1
4.19.32]
7 25 ms 27 ms 43 ms bu-ether11.tustca4200w-bcr00.tbone.rr.com [66.10
9.6.5]
8 21 ms 21 ms 21 ms 0.ae3.pr1.lax10.tbone.rr.com [107.14.19.56]
9 20 ms 24 ms 56 ms 66.109.7.38
10 * * * Request timed out.
11 41 ms 20 ms 22 ms ae0.cr2.lax112.us.zip.zayo.com [64.125.32.78]
12 31 ms 31 ms 32 ms ae1.cr2.sjc2.us.zip.zayo.com [64.125.31.233]
13 47 ms 58 ms 49 ms ae9.mpr2.sea1.us.zip.zayo.com [64.125.21.129]
14 85 ms 65 ms 47 ms 64.124.97.210.IPYX-099552-ZYO.above.net [64.124.
97.210]
15 45 ms 63 ms 47 ms gi2-3.dr03.sea.opticfusion.net [209.147.112.226]

16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * *
not working??smile
Ryan Dancey
No, that just means that the traceroute packets are blocked behind that last router for security purposes. Those systems change IP addresses dyanmically to thwart DDOS attacks.
Hedrik Holiday
So… 66.113.104.101 is also a dynamically assigned IP address?
Kitsune
Hedrik Holiday
So… 66.113.104.101 is also a dynamically assigned IP address?

You can pretty much be assured that every single IP address in that list of a traceroute could change at any moment. Typically, these changes don't happen often, but often your packets will take a different route to your destination, depending on many factors (maintenance, backbone changes, high traffic, etc.).

As for the final destination, in this case pfo.goblinworks.com, it is unlikely that it will change, but it has every right to. IF it does change, that's what DNS is all about. I will assume that you may not know what DNS does, so I'll give a quick explanation based on my knowledge (even though you probably already knew all this):
DNS is a network of information about what domain names translate into what IP addresses. Basically when you ping pfo.goblinworks.com, your computer, natively, doesn't know wtf that name means. Your computer is configured to ask your router "wtf is this name?" And your router is configured (usually by your ISP) to forward that question onto some public DNS servers in the backbone of the internet that all keep track of these things.

Now, if (and likely "when" ) that address changes, the company that hosts that server will send updates out to those public DNS servers to inform them that the IP address has changed.

Unfortunately, there are sometimes delays on how fast that change propagates to the rest of the internet, and there are chances that your computer might not get the update until "it's too late" and you've already tried to connect. The result would be you'd be trying to connect to the wrong IP, and well, you can't connect.
Hedrik Holiday
{smile} Yes, thanks Kitsune - I do know of DNS, and how it works. What you speak of with regard to updating DNS semi-automatically is more akin to DDNS (Dynamic DNS) which allows updates via an API, rather than through a 'manual' procedure.

And, 66.113.104.101 is in fact the destination IP (pfo.goblinworks.com) - thus why I was asking the GW folks… smile
Ryan Dancey
The routing table can and does change often. It is possible that if you ran the traceroute several times over the period of a month you would see different route table entries. It is possible that if there is a congested router between you and us it could change with every packet you send.

Inside our ISP, those routers change often for security reasons. The packet data that traceroute uses is obfuscated so that external users cannot selectively target those routers by IP address.

The physical router that a given IP address uses may change too. Even if the traceroute shows the same list of IP and names, the equipment may not be the same and the physical connection may not be the same. The connections may route over physically different hardware to make it impossible for an adversary to target a specific building or a specific strand of fiber.

Those are not necessarily protections we require, some of that stuff is now engineered into the internet's backbone due to the constant assault by DDoS and other malicious attacks on the common infrastructure.

The days when you could phsycially map two devices through specific physical routers and pieces of cable are over.
Kitsune
Ryan, I see now what Hedrik is specifically asking:

Are there any plans to change the DNS records of pfo.goblinworks.com to a different IP address, or did your provider give this to you as a "static" IP address for your server(s)?
Ryan Dancey
I honestly don't know how static we presume it to be.
 
You must be logged into an enrolled account to post