Well, that was exciting
May. 11th, 2018 07:09 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kengrLast night around 7 pm, I finally got around to inflating the tires on the bike Fay gave me. Been intending to do it for weeks, but never remembered to do it at a time when the npoise of the compressor would be ok.
Fast forward to about 4 am. Fortunately I was on the computer when there was this loud BANG! I checked around and finally realized that the front tire of the bike was flat.
Oh well, I wanted to take it to the bike shop anyway.
In other news, the DNS for my domain is *still* showing the Comcast address that it hasn't had for almost a month. The guy who does my hosting switched to CenturyLink then, and has been fighting to get the DNS working right.
For a short time this morning pinging it on the box that's hooked to a VPN gave a different IP address. Not the right one, but a *different* wrong one.
In the process of checking into who owned *that* address (Amazon, apparently) I noticed that the TTL (time to live) for the DNS result was only 24 hours.
That make me think that Comcast *has* to be part of the problem. I'm going to be calling them later today and asking why the [censored] DNS is *still* showing my domain as being at one of their IP address this long after things were moved.
Fast forward to about 4 am. Fortunately I was on the computer when there was this loud BANG! I checked around and finally realized that the front tire of the bike was flat.
Oh well, I wanted to take it to the bike shop anyway.
In other news, the DNS for my domain is *still* showing the Comcast address that it hasn't had for almost a month. The guy who does my hosting switched to CenturyLink then, and has been fighting to get the DNS working right.
For a short time this morning pinging it on the box that's hooked to a VPN gave a different IP address. Not the right one, but a *different* wrong one.
In the process of checking into who owned *that* address (Amazon, apparently) I noticed that the TTL (time to live) for the DNS result was only 24 hours.
That make me think that Comcast *has* to be part of the problem. I'm going to be calling them later today and asking why the [censored] DNS is *still* showing my domain as being at one of their IP address this long after things were moved.
