mastodon.cc is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon for Art

Administered by:

Server stats:

68
active users

#dns

18 posts17 participants0 posts today
Replied in thread

🏕️ my adventures in #selfhosting - day 92 ✨

My self-hosted #Ghost blog is almost ready for its debut. I have successfully re-imported all the media and fixed internal hyperlinks. Yay! (It looks and feels exactly like the old one, so most people won't notice a difference I think).

My current - soon to be former - Ghost blog (https://blog.elenarossini.com) which runs on a Ghost (Pro) plan will be active for another month... but I will stop payments in mid-April and thus my blog will be deleted immediately by Ghost.

I need your advice about something: is there a way to redirect traffic from subdomain1 [dot] elenarossini.com to subdomain2 [dot] elenarossini.com? With a wildcard maybe, so that all traffic to posts with a URL associated to subdomain1 are redirected to the new subdomain? Aside from the subdomain, the rest of the URL is identical.

And no, I don't want to tweak my self-hosted Ghost installation to use the old subdomain name. I prefer the new one for several reasons.

Any advice would be greatly appreciated! (Apologies if I had asked this before, but I tried some techniques with another blog and I wasn't successful).

Thanks!

Elena RossiniElena Rossini
More from Elena Rossini ⁂

Some great work from Denis Sinegubko yesterday on a VexTrio affiliate who has been compromising websites for years. This is complex research coming in three parts and aligns with some of our own.

A few highlights for me...sprinkling in some of our Infoblox work:
* The DollyWorld actor is a VexTrio (specifically a Los Pollos) affiliate since 2016. Given that Los Pollos dates to 2015, this is an old partner.
* Around November 20th, 2024, Los Pollos announced to their customers they would stop push monetization. I've written a lot on push monetization as a source of lingering evil. Whatever caused this change, it disrupted their affiliates.
* DollyWorld actor and the DNS C2 TXT systems we have been tracking carefully (after all, it's DNS) both switched to Monetizer TDS at that point. Coincidence?
* From Monetizer, both led to Propeller and delivered a variety of malicious content.
* I had originally used germannautica[.]com to get the VexTrio hook and then later was able to trigger participates[.]cfd (Monetizer) through the same site.
* Where VexTrio was just scams, the new TDS pattern also gave me malware

Most importantly -- scams pay! These affiliate actors are running for years on compromised sites and constantly updating their techniques. Why else would they keep going?

#dns #threatintel #cybercrime #cybersecurity #infosec #malware #scam #vextrio

godaddy.com/resources/news/dol

GoDaddy Blog · DollyWay World Domination: Eight Years of Evolving Website Malware Campaigns Discover how the DollyWay malware operation has compromised over 20,000 WordPress sites since 2016, using cryptographically signed payloads, distributed C2 networks, and sophisticated reinfection mechanisms to maintain persistent control.

Would anyone like to recommend a good domain name registrar? Or any I should avoid? Looking for services located in Europe, not owned by any overtly evil empire, must support DNSSEC and reasonable prices for .com and .org.

I've come across the below web page but I'm looking for recommendations from someone who has actual experience with using the services.

european-alternatives.eu/categ

European AlternativesEuropean domain name registrars | European AlternativesDomain name registrars are companies that manages the reservation of Internet domain names.

howdy, folks - it's been a bit since our last #hachyderm infra check in.

stuff in motion:

- ditching #terraform cloud & tf for #opentofu and #atlantis. we are just about to import our dev environment and put it through its paces.
- bringing #postgresql under ansible management. the team has been doing awesome work, and we've started to spin up dev nodes using the new playbooks. soon: production!
- moving #DNS zones away from AWS route 53. we chose bunny DNS as our provider and have been doing basic tests in dev. we'll likely prep our records for production this week with a plan for a cutover in one of the coming weekends.

and if you filled out our volunteer form and haven't heard from me in a bit - you're still on the list. we'll onboard a new batch of folks in the next couple of weeks.

:hachyderm: :blobfoxheartcute:

@hachyderm

Last week was another stakeholder meeting on #DNS4EU. #Whalebone provided a short overview of the project including a timeline. Public launch is scheduled for June this year. The talk elaborates on various considerations of the new #DNS project. I was mostly interested in the deployment aspect, the #DDoS slides and the #privacy and #anonymization mechanisms.

My personal main concern with the project is the absence of resolver technology. The project plainly uses the #KnotDNS resolver. Not a bad choice, but University taught me that diversity in the backend software introduces even more resiliency. Yet, as Whalebone is a #Czech company, it is apparent why they chose #KnotDNS exclusively.

The slides are public.

Replied in thread

@zbrando @morrick @ueeu You’re not wrong.

But, looking ahead, we can do so much better than the commercial domain name system.

Commercial domain names are a gold standard example of artificial scarcity. A domain name registrar cost next to nothing to operate. It’s tiny rows of text in a database. It could easily be free to own your own domain name – a huge part of what constitutes identity – on the Internet.

In fact, a non-commercial service has been operational for 24 years. It would be trivial to regulate that browsers in the EU implement support for it and work together with, say, @letsencrypt to ensure it can handle TLS.

That would be an amazing addition to the commons and a future-proof way forward that we could lead on with next to no investment.

Network I am unfucking in Maine had an issue. They tried to roll out a new VoIP subscriber in an area they had never done before, spent two days blaming magic (and #DNS) before calling me in.

I had never logged into any of the devices at this facility before in my life, didn't know how they were cabled, or even what was there.

Spent an hour and a half gathering credentials for things, mostly because they were slow in responding to all requests. Only spent about 20 minutes actually fixing the issue, and most of that was me remembering how to find a customer's port in an Adtran TA5000.

The problem as stated? "They can't resolve this host, foo.bar.com, it must be a DNS issue, but we can't find it."

Actual problem: the DHCP server config did not send the client a default route. Client could not resolve anything because it could not reach the DNS servers, nor anything else for that matter.

Added default route config to the DHCP server, found the customer in the TA5000, bounced their ONT port. Boom, headshot. Problem solved.

Tools I used to find this? ping, arp, route, and looking at the configuration. Before I got called in, they had gathered numerous packet captures, and provided all manner of useless supposition. Start simple, sometimes it is all you'll need. tcpdump is a great tool, but I never reach for it first. As for supposition, it's nothing but a huge waste of time, look at the facts. Can I ping this thing from the core? No. Can I ping this thing from the directly attached router? Yes. Okay, it doesn't have a route. Do I have a route for that subnet in the core? Yes. And so on....

Shit like this is why I despise the, "It's always DNS." bullshit.

Renforcement des protections des serveurs #DNS récursifs ouverts de @FDN pour une durée indéterminée : fdn.fr/renforcement-serveurs-d

Quelles conséquences ?
- Aucune pour les membres #FDN et #FFDN
- Aucune pour les personnes externes utilisant DoT et DoH
- Une indisponibilité pour le reste du monde

Que faire pour continuer à utiliser nos DNS? Activer DoT et DoH sur vos routeurs, box ou navigateurs (voir article)

Sinon utiliser d’autres DNS ouverts (liste non exhaustive sebsauvage.net/wiki/doku.php?i)

www.fdn.frRenforcement des protections des serveurs DNS récursifs ouverts de FDN | FDN - Fournisseur d'Accès à Internet associatif depuis 1992
More from FDN

🟣 Last day of #ICANN82 Community Forum here in Seattle! Our team stays committed all day long today to answer all of your questions about how Afnic can be your trusted partner for the next gTLD round.

♾️ Beyond actively participating in key discussions this week the Afnic delegation was thrilled and immensely proud to introduce Afnic Registry Services to the community.

💜 See you in Prague for the #ICANN83 Policy Forum!