AWS servers hit by sustained DDoS attack, Making us All Say "It's Always DNS"

Article

If you aren't familiar with Route 53 on AWS, it's a Domain Management module. So, the DDoS attack battered the records that tie IP addresses to FQDNs.

From 6:30pm BST on Tuesday, a handful of customers suffered an outage to services while the attack persisted, lasting until approximately 2:30am on Wednesday morning, when services to the Route 53 DNS were restored. This was the equivalent of a full working day in some parts of the US.

Amazon also encouraged users to specify the region their bucket was in when trying to update the configuration of clients.

What have we learned?

Anything can be attacked. Hopefully, you didn't have to learn that, as that is the mantra of anyone working in IT (Right after "It's always DNS"). After all, there is no cloud, it's just someone else's computer:

You still need backups, though I admit I'm not sure how you'd store DNS records (Though I can configure them in Cisco Command Line Interface (CLI)). Certainly you can write down "Yahoo! is 72.30.35.9" in notepad, but is there an actual style of how to keep DNS records on our machines? Let me know if so.

Also, that is the first time I visited Yahoo!s front page in years...it's very white-spacey and tabloid-y.

Comments

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

What Do You Need? [List of Offered Services]

2023 Version is here, at this handy Notion Page.

Building, Breaking, and Building A CRM with Retool

I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself. I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is: To have a GUI to add people to a NRM (Network Relationship Management). Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others). Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see. When you get set up, there's a plethora of resources you can use -- Incl

RUN TCP/IP | Morgan Lucas' Tech Portfolio

Search This Blog