James Watkins
@thejimwatkins
For some reason, 8's domain name is suspended. It could be a deplatforming. I am looking into this. This may have something to do with the Chyna war.
For those who would like an explanation of what is going on and how to theoretically solve the issue. I understand that 8kun has been through the ringer when it comes to DNS issues, however the "solution" that was used is a system waiting to fail. Any anons know of some reliable services the admins could use without worrying about deplatforming?
DNS Outage -- 8kun.top (Clearnet Unreachable, Onion Functional)
The clearnet version of 8kun.top is currently unreachable due to DNS failure. The domain itself is active and not expired, but all authoritative nameservers (dns1.8kun.top, dns2.8kun.top, dns3.8kun.top) are unresolvable. This means public resolvers (Google, Cloudflare, ISP DNS, etc.) cannot find or contact the domain’s authoritative DNS servers.
Because 8kun.top uses nameservers that are subdomains of itself, the entire DNS chain has become circularly broken. If those DNS servers go offline or their IPs aren’t registered as glue records, the whole domain becomes unresolvable.
Root Cause Summary:
Nameservers for 8kun.top are unreachable or missing valid glue records.
The .TOP registry still points to dns1.8kun.top, dns2.8kun.top, and dns3.8kun.top.
Without reachable authoritative DNS, all clearnet resolution fails (DNS_PROBE_POSSIBLE).
The onion site works because it doesn’t rely on public DNS.
Steps to Fix (Administrative Side):
Log in to the domain registrar
Confirm 8kun.top is not on clientHold or serverHold.
Verify it’s still active and paid up.
Fix or replace the DNS servers
If you still control dns1--3.8kun.top: bring those servers back online and ensure DNS (port 53 UDP/TCP) is open and serving zone data.
If you’ve lost them, switch to an external DNS provider (e.g. Cloudflare, Namecheap PremiumDNS, Route53) and update the registrar to use the new nameservers.
Set or update glue records
If keeping the same self-hosted nameservers, make sure the registrar has valid glue records for them. Example:
dns1.8kun.top → 135.148.43.6
dns2.8kun.top → 77.73.69.98
dns3.8kun.top → 77.73.68.181
Missing or outdated glue records are the most common cause of this exact outage.
Verify connectivity
Ensure the DNS servers respond on port 53 globally.
Check for upstream blocks, firewall rules, or BGP issues preventing access.
Rebuild redundancy
Use at least two independent DNS servers on different networks or ASNs.
Consider hosting one outside your main provider for reliability.
Tor access works but there's no images.
Current bread doesn't appear on the catalog.
couple of tor users and maybe an /etc/hosts user are there right now.
https://endchan.org/qrbunker/catalog.html
James Watkins @thejimwatkins For some reason, 8's domain name is suspended. It could be a deplatforming. I am looking into this. This may have something to do with the Chyna war.
https://x.com/thejimwatkins/status/1978481896003965119#m
Copied from an 8kun post:-
For those who would like an explanation of what is going on and how to theoretically solve the issue. I understand that 8kun has been through the ringer when it comes to DNS issues, however the "solution" that was used is a system waiting to fail. Any anons know of some reliable services the admins could use without worrying about deplatforming?
DNS Outage -- 8kun.top (Clearnet Unreachable, Onion Functional)
The clearnet version of 8kun.top is currently unreachable due to DNS failure. The domain itself is active and not expired, but all authoritative nameservers (dns1.8kun.top, dns2.8kun.top, dns3.8kun.top) are unresolvable. This means public resolvers (Google, Cloudflare, ISP DNS, etc.) cannot find or contact the domain’s authoritative DNS servers.
Because 8kun.top uses nameservers that are subdomains of itself, the entire DNS chain has become circularly broken. If those DNS servers go offline or their IPs aren’t registered as glue records, the whole domain becomes unresolvable.
Root Cause Summary:
Nameservers for 8kun.top are unreachable or missing valid glue records.
The .TOP registry still points to dns1.8kun.top, dns2.8kun.top, and dns3.8kun.top.
Without reachable authoritative DNS, all clearnet resolution fails (DNS_PROBE_POSSIBLE).
The onion site works because it doesn’t rely on public DNS.
Steps to Fix (Administrative Side):
Log in to the domain registrar
Confirm 8kun.top is not on clientHold or serverHold.
Verify it’s still active and paid up.
Fix or replace the DNS servers
If you still control dns1--3.8kun.top: bring those servers back online and ensure DNS (port 53 UDP/TCP) is open and serving zone data.
If you’ve lost them, switch to an external DNS provider (e.g. Cloudflare, Namecheap PremiumDNS, Route53) and update the registrar to use the new nameservers.
Set or update glue records
If keeping the same self-hosted nameservers, make sure the registrar has valid glue records for them. Example:
dns1.8kun.top → 135.148.43.6
dns2.8kun.top → 77.73.69.98
dns3.8kun.top → 77.73.68.181
Missing or outdated glue records are the most common cause of this exact outage.
Verify connectivity
Ensure the DNS servers respond on port 53 globally.
Check for upstream blocks, firewall rules, or BGP issues preventing access.
Rebuild redundancy
Use at least two independent DNS servers on different networks or ASNs.
Consider hosting one outside your main provider for reliability.
Test and propagate
Once DNS is restored, verify using:
dig NS 8kun.top @a.gtld.top (to confirm registry delegation)
dig 8kun.top @8.8.8.8 (to confirm resolution)
Allow up to 24 hours for full propagation.
Thanks Greekish
No idea what is going on. It is down for everyone.
Tor access works but there's no images. Current bread doesn't appear on the catalog. couple of tor users and maybe an /etc/hosts user are there right now.
For those wanting a TOR addy
http://w7m432cocr665kf5tlpcxojwldajr3njd2etcxwhpbrt44eemuxhp7ad.onion/qresearch/res/23738935.html#23739420
Prep for reemergence of Q?
the thought crossed my mind...time will tell.