As they should. If a domain name changes hands, the previous owner should have its ownership verification revoked.
1,187 karma · joined October 14, 2016
[ my public key: https://keybase.io/ruurtjan; my proof: https://keybase.io/ruurtjan/sigs/xboZ7fzACzFSzPjfaAEW3S4efJbiL2jkwdIcf1P-bOU ]
> A big pile of melting clocks. Vector art, flat illustration, wide stroke, dark background, bright neon colors. --v 5 --ar 2:1
You nailed it! Recursion, propagation, registry, registrar, registrant. Naming in the DNS could — ironically — use some work. But it's too late now, I suppose.
If you want to be better at DNS than >99% of your colleagues for the rest of your career, then invest a single day in reading those.
If you want to be better at DNS than >99% of your colleagues for the rest of your career, then invest a single day in reading those.
Location: Remote & async
Email: hello@nslookup.io
Pay: $100 per article
---
I'm looking for someone to write articles for https://www.nslookup.io/learning/. You'll need to have hands-on experience working with the DNS. Read a couple of articles to get an idea for the level of expertise needed. I'll prepare briefs with the outline of the article. Get in touch for more info.
You're using the list of DNS records from the original DNS RFC from 1987. Since then, a lot of new record types have been added: https://www.iana.org/assignments/dns-parameters/dns-paramete... Some of them, like CAA, SRV and AAAA, are used fairly often.
1. Ads through Ethical Ads or Carbon Ads. This is what I have with nslookup. It's at $500/month on these volumes: https://plausible.io/nslookup.io
2. An exclusive ad deal with a complementary service. That's what I have with whoismyisp.org. Think about what people are working on when they visit your tool, then find a service that they'll need right after that task.
3. Donations
4. Sell a course. i.e. "DNS for developers" for nslookup.io.
5. Add a paid API. i.e. DNS lookup API for nslookup.io.
6. Add a SaaS that does something similar, but more complex. i.e. monitoring DNS records for nslookup.io.
I'm also happy to give feedback on any side project (idea) you're working on.
I think so too. Thanks :)
- Don't know you can do it from a command line
- Don't bother remembering the order of arguments
- Want to see all record types in one go instead of repeating the command for every record type
- Would like to have the output clearly formatted
- Are currently on mobile
- Would like to see additional ip info for A/AAAA records
- Would like to check responses for multiple recursive resolvers without remembering all their IP's
- Would like to test GEO DNS
Started 1.5 months ago, and enjoying every minute of it! No longer occupying my mind with corporate power dynamics saves a lot of cognitive bandwidth, but to my surprise it has been replaced. I thought I'd feel more 'free', but instead I now feel self-imposed pressure to make this one shot count. I know my runway is limited, so every day that didn't tangibly contribute to bottom-line growth feels wasted. I can rationalize it by reminding myself that I can always get a job and try again later, and that I should be spending most of my time on mid to long-term goals that have delayed effects. But that hardly changes how I _feel_. All in all, I'm really glad I made the jump, and I'm still super excited about what I do now.
For many people it's more convenient to do DNS lookups on nslookup.io than googling the syntax and order of dig arguments, opening a terminal and entering it themselves. Plus, it can be convenient to get an overview of the popular record types, instead of doing 7 dig queries yourself.
> the same info
Nslookup.io provides more info than dig/nslookup CLIs: info about the A/AAAA IPs, logos for hosting providers, parsing DNS records, and more to come ;)
> In any case congratulations for finding a use case!
Thank you!