AT&T DNS

look if I'm wearing them I won't be able to act like I'm sleeping fast enough and my eyes already hurt so I'm not looking at dns or pfps or anything

I was still really young at that point, and even though up to then I had sold a company and gone to work for the company I sold mine to, I didn't have so much experience. Then I saw him again, in I believe 2008/9 at a conf in SanDiego. He was talking about the famous DNS issues.

They have been having a dns issue with each other that makes it so that psn just can’t connect while using their service. Happened for a few days straight at the beginning of the month and is happening again now. Have to do a custom dns setup to connect.

Come stay at my place and I'll go to yours! Today's challenge: a client's website is down so I have to talk to their IT guy to update DNS while my son has a meltdown because he can't find his drawing pad and favorite pencil. #AutismAcceptanceMonth

Wow, just heard @dakami passed. I first met him at Defcon in 2009, the year after his famous DNS presentation. We weren't close, but he was a beloved figure in my community, and i know many friends are missing him sorely rn. Much love to all of you. He was a special guy. </3

That's the thing about Dan. He was just always nice. DNS wasn't my thing and I remember just going up to him and he calibrated how much I knew and just started explaining it to me at that level. Didn't get arrogant about it. The dude was just nice and loved tech!

.us in (very big) boomtown USA - and the only reason I didn't put a TLD DNS block on that while I was at LANL

As evidenced by the thread discussed earlier - it can't handle things like http->https redirects or 308/301 redirects in many cases. It's just bad at handling that kind of thing. DNS round robin would require high level syncing which becomes another headache too.

Hitting my head over connectivity issue today, then it turns out that TLS 1.2 was not enabled! I guess at least it wasn't DNS... Thanks @JeremyMerrill

it still baffles me on why the heck i went to stan twt to find friends when i'm so bad at names & i can only remember 5 dns max & i can't even trust layouts too bc b1tches on this app change layouts 3x a day

I don't know - it could've been in error. It seems to resolve now, but it did not a few months back, which is why I switched away from it as I could get at it on a computer that did not use it for DNS.

I do wish I could do this at the router level, but @geteero devices don’t yet natively support DNS-over-HTTPS. So.

I was just looking at his Black Ops slides from 2002 again. I vividly remember him talking so excitedly about DNS even though it wasn't a core part of his talk. He thought so integratively about everything.

I'm pretty sure we use open dns. I've seen other comments about trust, but you can't unsee things and kids can innocently go to sites with horrific content. We also have our modem on timer. It goes off at 11pm and comes back on at 5am. It's not about trust. It's about protection.

I don't know. I hand registered it on 2020-08-28 It's been erroneously listed the DBL 4 times now. At least 2x in the past 4 months. I suspect that the @EpikDotCom DNS settings have had some impact on that, so I changed them tonight to another host.

Company use a custom, SQL based DNS system. Jr DBRE rolled 1 and performa an update without where clause on NS1, replicated to NS2 and NS3. SRE's don't have restore plan, last backup status is unknown. Party are looking at you, in dispair. You are the last hope. https://twitter.com/dmofengineering/status/1387918729988562947 …

PUG limits lifetime to 4 hours and doesn't store long term keys, but if the admin is logged in and malware running in their context, I can see that. Defender for Identity is good at detecting PtT (obviously could use SIEM too), but lots of FP's if DHCP/DNS aren't optimal :(

Ok so I dreamt that Twitter was broken asf and nobody could see pictures, nothing was loading at all...? And we couldn’t see dns anymore, it looked so weird

I've flip-flopped on this idea for a long time, but I think at this point DNSSEC shouldn't be harder to get right than Let's Encrypt, and is therefore worth doing. In a world where we don't TCP without TLS, DNS needs at least some cryptographic authentication.