Cat walking time. Nice and dark out there.
Be back soon. As if you care, kek.
This has been reported several times. It is DNS fuckery. I will be posting about this in the next half hour or so. Stay tuned.
>virus particle is a myth, no lab to this day has it isolated.
This is true. We are witnessing the lie of the century.
Wait for my report. I'm just reviewing it to make sure I got it right.
Heads up on the DNS fuckery
I haven't posted about this for a while and now I can't even point back to my previous reports on the matter because the breads have disappeared. What's up with the archive? Anyway, this is an important topic mostly because a great many anons are still unaware of the issue.
In order to not have to deal with my reports disappearing, I have decided to put them on my own board. The reports should be reposted on other boards but I won't be doing that myself. For this board, maybe somebody could make a pinned thread so that the issue can be discussed. Collecting problem reports would sure be nice so we can see how many anons are affected and to give advice on what to do about it.
While the DNS fuckery seems merely inconvenient right now, we can't afford to be complacent about it. The black hats have something in store for us. As far as I know, only 8kun is being targeted but what if they start targeting Bitchute or Rumble or any other "objectionable" site? Much chaos is potentially on the horizon.
I am reposting my reports here. Important updates will be posted here as well.
https://8kun.top/alleycat/res/968.html
DNS fuckery is still in progress
This report was last posted on May 2. This is an updated version.
This is serious. The situation is stable right now but there is clearly a plan to open a can of worms on the anons here. DNS servers worldwide are being seeded with invalid IP addresses for all of the 8kun subdomains. Apparently, this is being done through an exploit and many (possibly all) servers are affected to some degree. You can use the links below to monitor the situation. Note that "8kun.top", "media.8kun.top", "nerv.8kun.top" and "softserve.8kun.top" all share the same IP addresses so they do not need to be tested separately.
https://dnspropagation.net/A/8kun.top
https://dnspropagation.net/A/sys.8kun.top
Refresh the page a few times and look through it to see if some servers are showing a wrong IP address for the subdomain. For "8kun.top", there should be a set of 7 IP addresses. The bad DNS lookups occur randomly. This is happening with my own ISP and also with Google and OpenDNS. I am still trying to determine if Cloudflare is vulnerable. Although I have spotted an issue with Google and OpenDNS on just two occasions each, the fact that this has happened even once indicates that they are vulnerable.
Now, the key to this is what is called the TTL which means "Time To Live". It is normally 60 seconds for this site. This means that, if your DNS server gets seeded with an invalid IP address then you need to wait till the TTL runs out for your DNS cache to refresh and get a new address. I have observed that the TTL for the bad IP addresses exceeds 60 seconds (up to 300 seconds, it seems). Note that this TTL is not necessarily adhered to. Some DNS servers (meaning the one supplied by your ISP) may ignore this value. That is, it may take a longer period of time for the bad IP address to get flushed out of the cache. I don't know this but you should keep it in mind if the site seems to go down for a long period.
There are three critical subdomains involved: "8kun.top", "media.8kun.top" and "sys.8kun.top". If "8kun.top" fails, auto-updates will fail and the catalog will fail (the site will become inaccessible). If "media.8kun.top" fails, images and other media will not load. The two will almost never fail at the same time. This is another reason why it may look like just a temporary glitch. If "sys.8kun.top" fails, posting and captchas will not work. Board administration also runs through this subdomain.
I have seen very few problem reports so it is impossible to gauge just how many people are affected. Most of the time, a bad IP address will be unresponsive and your access to 8kun will fail silently. It is possible that you may get an error message from your web browser about an invalid security certificate. Some of the IP addresses belong to Facebook and a few anons have reported getting what appears to be an error message from Facebook. When you see an error message, just close it and try again in a minute or few.
There could be hundreds of bad IP addresses being circulated. I am no expert on DNS or Internet security so I have no conclusion to make about the distribution. I will note that a cursory examination suggests to me that the addresses are all under the control of possibly just one Internet authority. Look here:
https://en.wikipedia.org/wiki/List_of_assigned_/8_IPv4_address_blocks
Next post: what might be coming and some hints on how to prepare.
DNS fuckery: what is to come and how to prepare
If you perform the DNS Propagation Test as suggested in the previous post, you will notice that some servers exhibit the problem regularly but others seem to be unaffected. The DNS attacks may not be totally random. There may be a purposeful pattern which targets some more than others. If the frequency of attack on a particular server is very low then you may never spot it. I have seen two instances of a bad IP address from Google but separated by days. OpenDNS gave me two in the same day but that was after weeks of testing. On the other hand, my ISP will feed me a bad IP address several times a day. This is all very circumstantial but I'm not inclined to write a bot to hit the DNS servers in order to gather statistics.
There are thousands of DNS servers spread around the globe, each serving a specific market. If the ultimate target of the attack is YOU then only certain upstream servers feeding the local ISP market would need to be targeted. I don't have any idea what upstream server my ISP uses but I can say that it is not Google or Cloudflare or OpenDNS. Since most people accept whatever default DNS server is assigned by their ISP then the targeting makes sense. Switching away from your default DNS is a good idea but you shouldn't expect that to keep you safe if the black hats decide to put on a full-scale assault. All DNS servers should be considered suspect until proven otherwise.
Here is what we need to be prepared for:
The exploit which is being used to seed bad IP addresses can clearly be used to modify the TTL (Time To Live). Simply extending the TTL to an hour or so could take down the site or at least reduce the traffic considerably. The site operators and Vanwanet would not even know what happened. This would work like a valve. Open the valve to let the traffic through and then close it for any desired period of time. This could be controlled geographically like a wave sweeping across the globe. As it is right now, the TTL is low enough that the fuckery looks like a temporary glitch. In addition, bad IP addresses could be seeded more frequently but, judging from I'm already seeing from my ISP, the frequency is already high enough. Bumping up the TTL could lock me out of 8kun indefinitely if I were to rely on my default DNS server.
Savvy anons know exactly what to do because we've been through this before. For now, you should change your DNS server but this is not a long-term solution if the attack escalates. Think logically: if they REALLY want to take us down then no DNS server is safe. In the event that you do get hit with a bad IP address and the TTL is set to a long period then you should know how to flush your system DNS cache (though this won't help if your DNS server is still holding the bad IP address in its own cache). The ultimate solution is to not rely on the DNS servers at all. Most anons have probably (by now) learned the trick of modifying the "hosts" file. These are the currently valid IP addresses for the site:
sys.8kun.top: 185.165.190.88
8kun.top, media.8kun.top, nerv.8kun.top, softserve.8kun.top:
94.103.81.80, 94.103.82.74, 94.103.94.73, 109.234.38.4, 193.178.169.19, 195.2.92.96, 195.2.93.193
DNS server IP addresses:
Cloudflare - 1.1.1.1 and 1.0.0.1, Google - 8.8.8.8 and 8.8.4.4, OpenDNS - 208.67.222.222 and 208.67.220.220
I am not providing any instructions on how to implement these solutions because that depends on what operating system you are on. Also, I have zero familiarity with phonefagging and I have no idea what can be done in that context. Do your own research to prepare yourself.
DNS fuckery: possible attack vectors
So what exploit could the black hats be using to target the DNS servers? I have no idea. I'm not an Internet expert so I can only take a guess. These two articles might be helpful:
https://en.wikipedia.org/wiki/dns_cache_poisoning
An anon posted this one: https://kb.isc.org/docs/cve-2021-25216
Interesting thing about the second article is the post date (April 28). This is just two days before I started noticing the fuckery. Holy hell. Is that a coincidence? To make matters even more spoopy, Dan Kaminsky died recently. He was an Internet security researcher and he gained prominence for his work on patching a DNS "cache poisoning" vulnerability in 2008. What was he working on recently? Something that somebody did not want to become public?
https://en.wikipedia.org/wiki/Dan_Kaminsky
That's it for now.
I have no additional posts. That's it until the situation changes. So far, it's been stable for three weeks.
Eating pizza. Anybody want a piece? Sorry, you can't have one. All for me. All of it.
Eating my pizza. You can't have.
The real Pizzagate happened in 2011:
https://www.salon.com/2011/06/02/donald_trump_responds_pizza/
So quiet here. The shill bots got bored and left.
The Graveyard Shift is having a Pizza Night, it would appear.
They want us to be afraid of each other, our dogs and cats, and now chickens.
Do I sense an agenda here?
Master Chief fell from the sky. No parachute though.
From the article: Pro-Israel lobby AIPAC ran an ad falsely linking US Rep. Ilhan Omar to Hamas
I see. Facebook protects the joos.
Find some boobs. Though not exactly "productive", I guess.
It's just a dream so next time grab a gun and let everybody have it.
I love doing that when I dream of zombies.
Baker, you missed the third post in the "DNS fuckery" series: >>13725983
This one should not be on the list: >>13726025
How about this for the title: DNS fuckery - black hats targeting 8kun via the DNS servers
Baker,
Yeah, you must be tired, kek. Just copy this:
>>13725977, >>13725979, >>13725983, >>13725989 DNS fuckery - black hats targeting 8kun via the DNS servers
How long you been awake, Baker? I know what it feels like. Ugh.
19 hours. Before I got a good rest, I think it was over 28 hours (programming binge).
I'll probably be paying for it later with 12-hour rest periods, kek.
Got a LOT of sleep last week though. The perils of being retired with no job to wake up for.
I believe you are correct but the former has entered the lexicon.
Like "toe the line" versus "tow the line".
Baker, another oopsie:
>>>13725948, >>13725983, >>13725986, >>13725969, >>13725981 Allison Mack’s Sentencing for Involvement With NXIVM Cult Set for June
13725983 is my post. Repair job:
>>>13725948, >>13725986, >>13725969, >>13725981 Allison Mack’s Sentencing for Involvement With NXIVM Cult Set for June
Maybe I'm tired too? Didn't notice the extra ">". Meh.
>when I get too tired, I start to see rabbits in the corner of my vision
Kek. Reminds me of when I started doing night shift as a cleaner. Couldn't get used to the idea of sleeping during the day so I would often go without sleep. I would hallucinate paper clips everywhere on the carpet. I knew that they weren't real when they didn't make a clattering noise as they went up the vacuum wand.
Maybe you just need to boycott a few rest periods and make yourself more tired.
Be careful what you wish for. Oversleeping can be as bad as undersleeping. Oversleeping when you don't need it is bad. If you need it then take it. Depends on the individual. I have a fucked up sleeping pattern (been that way all of my life) so don't take advice from me, kek. My record is 16 years of sleep without even waking up to pee. Fucked if I know why I did that.
Baker, looks fine on my account. Thank you for your service.
But stay away from baking when you're fighting your sleep demon. Kek.
Since you're so tired now then surely you will sleep well today?
Did you miss reading my DNS fuckery posts? Go back and read or re-read. I specifically pointed out the security certificate problem and Facebook.
My posts are in this bread. Search for "dns fuckery".
Taken care of, anon. Your screen cap is not needed.
>but use tor to avoid this message
An anon has reported this error message coming through TOR which also relies on the DNS servers to reach 8kun.
Hmm, I think I should correct that. I think the anon was using clearnet over TOR and not straight TOR. Don't exactly remember. Until more info comes in, we don't know for sure if TOR is safe.
Do we have a team of bakers here or one baker with four different IPs?
Sincerely, Confused
Which is better: death by virus or death by vax? Hmm, that's a tough choice.
Obviously, we are going to squeal about it. There goes your secret.
But, seriously, you're from another planet, right? Who on your planet is not supposed to know?
Okay, have to ask a dumb question. Why must "time and space and matter" be created but not the "spiritual realm"? Why can't it be the other way around?
Weasel words.
Working up to the conversation between the alien and John Cleese in the crappy remake of Day the Earth Stood Still.
Nobody here believes you therefore nobody on the outside will be convinced.
You could tell the whole world yourself and nobody would believe.
The secrecy is unnecessary. You lie.
Different kind or superior kind? Sounds like racism, kek.
Six-hour bread. Can't believe I stayed for the whole thing.
Masochism. It bites.
Welcome to the Ship of Fools, kek.
Need moar shitposting! Baker wants this bread filled. Hup, hup.