A slightly more complex, but much more responsive way would be to set an NS record of `where-is-the-iss.shkspr.mobi` that points to the IP of your VPS.
Then run a program that listens to UDP/53 and TCP/53. Have it respond with a DNS packet that's only dynamic in the LOC record and message ID. Not fully compliant with the DNS spec, but good enough for this use case.
You could cache API response to combat rate limiting.
I did actually find nslookup.io while researching whether I should build this or not, and based some of my user interface choices off what I saw there.
I ultimately decided to make inspector.improvmx.com because I wanted something simpler.
A lot of our customers at improvmx are non-technical (yet still want to figure out how to setup their DNS entries themselves or with our help, and hopefully never touch it again). I think nslookup.io is more powerful and gives more information, but a lot of our customers would take one look at the site and immediately their eyes would glaze over from the technical overload.
So it's ultimately less about things you could add, but rather the simple lack of features is something I'm looking for, which is targeting a different use case.
Anyway, please let me know if you have any thoughts/suggestions for inspector.improvmx.com!
Yeah, your tool is a lot simpler and can be less overwhelming for people who are not familiar with DNS. Don't think I'll remove any features from Nslookup. Good to have multiple DNS checkers for people to choose from :)
A set of free online internet infrastructure inspection tools. Think DNS, IP, ASN, WHOIS, email config, etc. It will replace my current main project nslookup.io when it'll launch.
Beta is open at https://beta.nslookup.io (registration wall for now, but I'll remove it at launch).
which loophole? I didn't see it mentioned in the article.
and this quote is not correct:
> Note that an email doesn't need to pass both DKIM and SPF. Just one is enough to validate an email.
Unless it was said in regards to DMARC, it usually depends on the mailfilter of the receiver. If it was said in regards to DMARC then it's just another point why DMARC is bad.
I've done this for https://www.nslookup.io. Downloaded a list of the 1 million most popular domain names, scraped TXT records for them, and mined common patterns to add formatting with logos to the TXT records section.
Then run a program that listens to UDP/53 and TCP/53. Have it respond with a DNS packet that's only dynamic in the LOC record and message ID. Not fully compliant with the DNS spec, but good enough for this use case.
You could cache API response to combat rate limiting.