A browsable map of internet infrastructure. Not just a collection of lookup tools, but it also interlinks results, so you can navigate linked assets as well. Think: DNS lookup -> SPF record -> mail provider's SPF record -> IP address details.
That's not even close to what "wiki" means. Couldn't you have spent two seconds looking up the term that you're using (a community-owned content/knowledge graph that's "collaboratively edited and managed by its audience directly through a web browser") before debasing it?
You've confused "wiki" and "encyclopedia"—getting them exactly backwards. Wikipedia is an online encyclopedia that's a wiki.
You're creating (or, at least, aiming to create) an online encyclopedia. But it's not a wiki.
"Wiki" normally refers to user-editable sites, while the graph part is normally implied from being a website. Perhaps Wiregraph would be more accurate? Maybe Wireview? These kinds of networking sites are often called looking glasses, so Wireglass might also work, besides the confusion with the material.
You're right that it doesn't do the name Wirewiki justice yet. I've got so many things planned to add at some point, much more than just DNS. Check again in 2 years' time ;)
> The list of servers you're going to get with a naive scanning approach is not what you want.
Absolutely right. I'm doing uptime monitoring and a handful of checks (udp/tcp, nxdomain, dnssec, dns filtering) before listing them, but I feel like it could definitely be improved. Would love to talk! I'll send you an email.
You're the second person in these comments who points out faux name server redundancy. Interesting. I hadn't considered it as a major theme, but I'll move it up the list a little.
> Authoritative drift.
This is why I query all authoritative name servers (as well as delegating name servers when querying NS records) in the DNS propagation tool. I haven't seen any other site do this. This feels like such an obvious thing to me, but somehow I'm the only one.
> 1) Include a link to dnsviz.net to check on the DNSSEC status of domains.
I use DNSViz all the time. They've done a great job of displaying the entire trail and helping debug DNSSEC issues. But it's a bit too detailed for my liking. I'm thinking about how I would add this to Wirewiki. What to show and hide by default, how to format it, etc. Adding something similar is pretty high on my list for Wirewiki.
> 2) Shared fate [...]
I do already show ASNs for A/AAAA records, but adding those to NS and MX addresses as well would be useful. I'm a bit hesitant to add more data to the overview, but a separate page that shows an analysis of shared name server resources could be useful indeed. I've added it to the list.
> 3) displaying whether a domain exists on popular block lists would be awesome.
Absolutely. Already on the list :)
> You could spend the rest of your life building this and never actually completing it, be careful!
Haha, I've already spent 5 years, and I don't mind to keep going as long as it's interesting and sustainable!
How do you see this positioned against something like MXToolbox? There seems to be a lot of overlap in features as it is today so I'm interested in your longer-term vision for wirewiki.
There are a ton of online DNS tool sites, MxToolbox being one of the largest.
I like the idea of evolution (diversity + selection) applied here. Many people building it differently and letting the market decide what's most useful.
My take on this space is making it a browsable graph instead of 'just' a collection of lookup tools. The internet _is_ a graph, and it often makes sense to inspect linked resources (Domain name -> name server -> IP address, for example).
As for the longer-term vision, I'd like to make this graph as complete as possible. It now only has DNS-related tools, but adding ASNs, BGP data, hosting providers, etc. would make the existing tools more useful with every addition.
i remember watching your DNS course, it was very good! Do you have any other resources that you like? where i can learn internet infra, dns or anything. Thanks!!
Depends on how you prefer to learn, but here are a few suggestions.
I've heard good things about the Computer Networks book by Tanenbaum and Wetherall, but I haven't read it myself. Very broad and comprehensive.
The most hardcore way would be to make reading RFCs your hobby. It can be tough to get through, but if you regularly take half an hour to do it, you'll learn so much.
I've recently started a course at https://classes.pracnet.net/, which is good too.
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.
A browsable map of internet infrastructure. Not just a collection of lookup tools, but it also interlinks results, so you can navigate linked assets as well. Think: DNS lookup -> SPF record -> mail provider's SPF record -> IP address details.
reply