My favorite thing about nslookup is it's clear which server it's querying to get its information.
870 karma · joined September 8, 2015
My favorite thing about nslookup is it's clear which server it's querying to get its information.
Yup, I wrote a DNS server that does just that. So, to find your public IP, you'd type the following:
`dig @ns.sslip.io ip.sslip.io txt +short`
It'll return your public IP.
[removed comments about unrelated services]
I _think_ I can retire, but I like software, and I like working with people. And lying on the beach bores me after a day.
That's a bad pairing experience, and I've had a handful of those in my last five years of pair programming.
On occasion I've said, "Look, why don't you tell me what to do, and I'll drive?"
But I think that the larger issue is that some developers are better at solo'ing than pair'ing, and there's nothing wrong with that, and at the company I worked (Pivotal), we'd find positions for the people who were more inclined to solo.
I skipped eighth grade, and I feel the same way.
("amphetamine" loosely meaning energy level, not meaning the actual drug family)
I'm 57, and I completely agree.
I experienced being treated differently when I was playing a very attractive Blood Elf Warrior in World of Warcraft ten years ago: a fellow adventurer would continually give me gifts (valuable in-game items).
The third time this happened I realized he wasn't being generous—he was courting me! I had to come clean.
I messaged him, "Dude, I gotta tell ya: I'm not a girl in real life."
"You're not?"
"No, I'm a balding man in his mid-forties."
Long pause, and then he replied, "I gotta take a cold shower."
I never heard from him again, but he seemed like a nice guy who was trying to get a girlfriend by doing nice things for her, and I hope he found what he was looking for.
- A FreeBSD firewall (requires continuous patching)
- 6 DNS/NTP servers (don't ask!), most of which are in the cloud
- 2 VMware ESXi hosts
- 3 ethernet switches (an 8-port 10Gbe, 24-port 1GBe, 8-port 1GBe)
- 2 WiFi Access Points
- 12TB TrueNAS server
- 2 laptops, 1 desktop
- countless VLANs, countless VMs.
Effectively I run my own AWS. But it comes at a cost: countless evenings & weekends. Endless updates (OS, BIOS, firmware), periodic hardware failures.
Also, as pointed out, security. My unpatched DNS server was compromised, and the intruder managed to get root on my server (this was back in '99, before BIND was heavily re-vamped for security).
Self-hosting is a labor of love, but I'd be hard-pressed to recommend it to anyone who didn't enjoy it.
We had a couple of problems that IBM's competitors didn't have. For one thing, we couldn't make too powerful a PC that might cannibalize the minicomputer sales (AS/400). IBM made much more money on an AS/400 than a PS/2 model 95.
Our cost structure was too high. How high? We lost $1 for every $100 we sold.
Part of the reason the cost structure was high were the number of IBM'ers: I worked in an office of about 15 people supporting the NY/Long Island region. Four years later, it was down to 1 person.
Another reason was our physical costs were high. For example, we couldn't buy RAM from Intel; we had to buy RAM from IBM (which was fabbed in Kingston, NY, not to be confused with the Kingston RAM mfr).
Also, we were struggling to get the correct mix of sales channels. For example, we couldn't sell PCs directly through the IBM sales force (too expensive, IIRC it added 36% to the sales cost). Instead, the IBM sales force would partner with dealerships (which added 21% to the sales cost). The web didn't exist yet, not really, so we couldn't sell through there. We could have done direct-response (an 800 number, like Dell & Gateway were doing), but that took a while to spin up. And it was similar in cost to selling through dealerships. Also we didn't sell through distributors, which was the least-expensive channel (16% IIRC).
I remember looking at the price list. We had two levels of dealers: those who bought large volumes, which typically purchased equipment at 30% off list, and those who worked in smaller quantities, which would get ~20% off list.
As the PC Market became more competitive, we couldn't afford high list prices (we were too expensive), so one of the ways we brought down our list prices was to shrink the discount we gave to the dealers.
The dealer was not allowed to sell online or via computer magazines: there had to be in-person contact. That helped prevent the Atlanta dealers from poaching the NYC dealers' business.
It's easy to armchair-quarterback the decisions IBM made, but a lot of those decisions were nuanced. For example, you could say, "Why didn't IBM have an 800 number to buy PCs?". And the answer is that a lot of our biggest customers were corporations, not individual consumers, and they felt more comfortable purchasing through a dealer they trusted.
I do love a four-day work week, but with 8-hour days, and I've been lucky enough to pull that off for the last 15 years. There's a downside though: it makes switching jobs much more difficult because few companies want to hire someone who only works 4 days/week.
I'd argue that the key word here is "trauma"; I think _adversity_ can make you stronger (more disciplined, and more focused), but I think that Dr. Bernstein is using the word "trauma" in its technical, medical, sense, i.e. "Psychological trauma is caused by an adverse experience, or series of experiences, that result in an injury that changes the way the brain functions, impairing neurophysiological, psychological, and cognitive functioning." [0]
In a similar vein, with respect to "there are no atheists in foxholes", A three-tour-of-duty-in-Vietnam captain in the US Army (Harry McMenamin) said, "I was an atheist when I was in Vietnam, and I was in a lot of foxholes. There are atheists in foxholes."
AMIs are a pain to publish: you need one for each region, and AWS keeps adding regions, and publishing is a challenge (you need to be a citizen to publish to the Gov regions, and you won't believe how hard it is to reliably publish to the China region, at least back in '18).
AMIs should be S3 blobs like GCP, and that makes everything simpler.
And, while we're at it, Key Pairs should allow elliptic curve (ssh-keygen -t ed25519 ...) instead of forcing us to use RSA.
I have found that to be true in at least one case—I had built a custom DNS server in Go (statically linked), and originally planned to run it in a container, but on further reflection realized the container brought no added value, and it was much simpler to write a systemd service control script than to bring in the extra baggage of a container ecosystem to run the DNS server.
Two weeks after being put on Lipitor I began to suffer chronic insomnia for the first time in my life: I had good sleep hygiene (almost perfect), consistent exercise, and minimal caffeine (only in the morning, only before 9am).
The problem lay in my body chemistry: insomnia was not an uncommon side effect of Lipitor. The fix? My doctor swapped out Lipitor for a different statin.
I feel there's merit to a singleness-of-purpose within an organization, and ACLU's attempt to juggle "12 or 15 different values" detracts from its effectiveness.
I was only diagnosed pre-diabetic (fasting glucose > 100) the last year before I blossomed into a full-blown diabetic.
My parents were pretty strict about sweets, but once I was on my own my diet quickly spiraled into an orgy of chocolate & sugar.
I had no family history of diabetes, I was never overweight, and was always athletic.
Admittedly, this is a sample set of 1, but I remain convinced that my voracious appetite for sugar played into my diagnosis. I no longer eat sugar (with the exception of fruit).
I wouldn't say "better" (I don't know want a flame war); I'd say "different". I like FreeBSD, and use it for my firewall (I find `ipf` more intuitive than `iptables`).
I also use it for my fileserver (FreeNAS/ZFS).
I think containers (Docker) works better on Linux. Containers (namespaces & cgroups) are a Linux-thing.
And getting email to the internet at large was no mean feat: I remember having to do a slew of UUCP addressing to get an email from AT&T to the internet (something along the lines of "astevens@redhill3!ihnp4@mit.edu). It was the wild west.
I never told my parents about it because I would have gotten yelled at.
At camp we put crickets on the electric fence, but nothing happened to them, so I grabbed the electric fence, and that was a powerful jolt. I never did that again, either.
It wasn't quite the solution I was looking for. I wanted my DNS server to "just work" for people who downloaded it—I didn't want to force them to re-configure systemd to accommodate my software.
Tweaking my software to accommodate systemd.resolved took ~4 hours. It was an enjoyable dive, but I'd rather not have had to do it on the first place.
I continue to think it's a bit of an overreach for Fedora to include a DNS server by default.
I like Linux, but I have mixed feelings about systemd, especially when I discovered that systemd runs its own DNS server, which prevents the DNS server I wrote from binding to port 53 using INADDR_ANY. Instead, I had to write code to enumerate the interfaces & corresponding IP addresses & bind to each one separately. Systemd's decision to run their own DNS server is a bit of overreach, IMHO.