So it has come to this...

"Out, but with a W - has found the answer" (belg) 05/16/2016 at 11:27 • Filed to: None

1

10

oppositelock.jalopnik.com no longer works, so I guess it’s time to truly embrace Kinja as our malevolent overlord sole domain.

EDIT: never mind, DNS troubles all around!

EDIT 2: DNS problems solved, still lost .jalopnik :(

Xyl0c41n3 > Out, but with a W - has found the answer 05/16/2016 at 11:31

1

It stopped working a while ago.

Out, but with a W - has found the answer > Xyl0c41n3 05/16/2016 at 11:35

0

Still worked until an hour ago over here, possibly due to caching(?). I’ve since started encountering DNS errors across all Kinja sites, so I wonder whether it’s on my end or just some general hiccups.

TheTurbochargedSquirrel > Out, but with a W - has found the answer 05/16/2016 at 11:48

0

Works for me. Not that I was actually here before the .kinja switch.

Out, but with a W - has found the answer > TheTurbochargedSquirrel 05/16/2016 at 11:52

0

According to Xyl0c41n3 it stopped working a while ago, so it’s probably due to DNS caching if it still works on your end (and worked over here until just now).

Smallbear wants a modern Syclone, local Maple Leafs spammer > Out, but with a W - has found the answer 05/16/2016 at 11:55

1

I’ve been having DNS issues on and off for weeks with Kinja.

Smallbear wants a modern Syclone, local Maple Leafs spammer > Out, but with a W - has found the answer 05/16/2016 at 11:56

0

I’ve had to switch DNS’s a couple times today for oppo. everything else seems to work.

derf > Out, but with a W - has found the answer 05/16/2016 at 12:30

1

It actually looks like DNS caching of negative responses is just prolonging some previous issue. If you ask for oppositelock.jalopnik.com from jalopnik.com’s authoritative nameserver, it comes back as a CNAME for kinja.com. The TTL is set to one hour, so it should sort itself out within that time frame, but it’s not uncommon for ISP DNS servers to do their own thing when it comes to caching regardless of what the TTL says.

TLDR: oppositelock.jalopnik.com still resolves according to jalopnik’s actual name servers, so it should work again for you at some point.

> server dns1.p05.nsone.net
Default Server: dns1.p05.nsone.net
Address: 198.51.44.5

> oppositelock.jalopnik.com
Server: dns1.p05.nsone.net
Address: 198.51.44.5

oppositelock.jalopnik.com canonical name = kinja.com
jalopnik.com
primary name server = dns1.p05.nsone.net
responsible mail addr = hostmaster.nsone.net
serial = 1458172266
refresh = 3600 (1 hour)
retry = 600 (10 mins)
expire = 604800 (7 days)
default TTL = 3600 (1 hour)
>

derf > Out, but with a W - has found the answer 05/16/2016 at 13:07

1

I just had oppositelock.kinja.com (not jalopnik) and one other .kinja.com name fail to resolve on me, and then resolve again a few seconds later. My guess is something is wonky with at least one of the DNS servers for kinja.com, so if your request gets round robined to the wrong one it may come back as a negative response (which could then stick around for a while if your ISP’s DNS server decides to cache it).

RallyDarkstrike - Fan of 2-cyl FIATs, Eastern Bloc & Kei cars > Out, but with a W - has found the answer 05/28/2016 at 07:33

0

The DNS servers our provider uses are crap - have you ever changed your router settings to use Google’s free DNS servers instead? I did ages ago and it’s been vastly more reliable since...

Go into your router settings and set your DNS servers to 8.8.8.8 and 8.8.4.4 and see if it helps! :)

Out, but with a W - has found the answer > RallyDarkstrike - Fan of 2-cyl FIATs, Eastern Bloc & Kei cars 05/28/2016 at 07:41

1

Great tip, I actually switched to Google’s servers at the time of this problem, but it still persisted for a couple of days. The problem’s gone now, so I’d chalk it up to Kinja nibbles.