Tool bulk nameserver deleted domains

[Jonh Borin]

hello guys Are there a tool that gives bulk nameserver to previously ended domains

 

[twiki]

@jmcc

Some valid points here.

Note: Just realized you're behind HosterStats.... I have limited time so I was skimming through it. My apologies.

To be honest I've heard about your site multiple times but never used. What is your monetization model, may I ask?

RDAP: I know there will be gated and tiered paid access to data. The future is going there anyway; do you need to access your car's seat heating? But that is already factored in. For the moment we have what is needed. For the future we will obviously pay for data. In fact we are paying for data even before starting.

The scalability aspect:

Ehe... you've just hit the nail in the head. That's the key here.

I'd say that not every startup out there is going to get that key. By looking at your site, can tell you know well about this.

Fortunately, this is right down my alley.
Started in 1997 or so with my first search engine... at the end of an 33Kbps leased line (copper wire) internet connection which was costing me an arm an leg back then, it was that expensive.

Building things that scale is my specialty. And it does require a lot of experience and a lot of work. Especially with optimizing large databases and stuff. But it goes far beyond that. Syncing a swarm of bots and making all working smooth without anything crashing each 10 minutes isn't an easy job.

TBH I have been considering some of the worst applications, where the above is just... piece of cake.

What I always wanted to crack is the area which Ahrefs and Majestic are in, and nowadays Semrush has cracked. But that ain't for the faint hearted. You need not only some serious power, petabytes of disk space and network, and a LOT of funding. Great engineers, large team etc. So this is still nice to look at but probably out of my league.

Downsizing a bit, I've been running my network(s) over a few years doing lots of different things and preparing for it. Still doing that. It is a challenge. But it is already up to that. 80% of the tech needed is already done more or less; with codebase in. What is not yet done is putting together everything, and aspects like sales, case use, niches etc. Plus the user interface / layer. But all these are the fun part, right?

I have zero doubts in the project at this time.

In fact I have been running a couple startups over the past doing various things, for example I had an url shortener that did a few things, such as an A/B rotator test, tracking, blocking some unwanted traffic and providing some stats. It was profitable from the first month; but it was scaling slow so I decided to cut it loose after a bit. There's experience. That's what matters.

Anyway, once you have a vision things start unfolding. And it's an amazing experience that opens so many avenues.

I've already opened to the world a few things which are unique, from my backyard. Such as my formerly private appraisal tool. There are lots of other things which are NOT live yet but there are gaps in various industries where they fit nicely. I prepare a lot, and launch only a very little = when I am 100% sure of stuff. Note, I already have paid user requests for it (got my first 2 days after launch?) but I'm postponing them for now. Got very good feedback + a bit of acid ones which only stirred me to get even better.

There's more to come and fortunately it's based on work previously done over a couple decades, just adapted to today's needs and user pains.

Edit: I am the unconventional ( tech ) guy.

Where everyone tells me it's not possible, I wanna try for myself.

Where everyone tells me you have to do that, I want to do the other - the one they tell me don't do that, ever. Finding ways to do that, always.

Same is with domaining.

I've carved myself a niche in repurposing dropped names. If you look at the sales reports, there's no direct domainer competitor that does it. A few do but... not on the same scale. I feel kinda lonely in my niche.

In tech, it pays off to have unconventional, lateral thinking. I often have to duck cause bricks are coming at ya, but hey, it's part of the fun. Being able to finish things, provide stuff, at least differently if not unique.

 

[twiki]

@jmcc

My favorite personal saying about the above is:

Say if I'm on a beach and everyone is yelling and running to the left, I would go to the right to see what they are running from, and how I can tackle that thing my way. Perhaps even by going into water, who knows.

I always trust my instinct. And while I listen (I do listen to your advice above) I still don't trust so much what others have to say to me, especially about limits and limitations. Those are there just to be broken - somehow.

Most of my businesses have always been deemed impossible and are still deemed impossible, including one I've built 15 years ago and is still running and I'm rebuilding right now (totally unrelated). Fighting directly with some major local corporations and again with no direct competitor in the niche. 15 years later, yes - still no direct competitor whatsoever.

It helps to try to be different. It doesn't get you well understood though.

Some folks are really willing to not understand anything and say you're a fraud and throw bricks at ya. I just do my work and that's my proof, nothing else. Whatever is running you, mate. Peace.

Liked your feedback, thanks.

 

[jmcc]

@jmcc

Some valid points here.

Note: Just realized you're behind HosterStats.... I have limited time so I was skimming through it. My apologies.

To be honest I've heard about your site multiple times but never used. What is your monetization model, may I ask?

Research, reports and some site monetisation. I had been planning to add the registrar and hoster statistics side back to the site but have been a bit busy.

RDAP: I know there will be gated and tiered paid access to data. The future is going there anyway; do you need to access your car's seat heating? But that is already factored in. For the moment we have what is needed. For the future we will obviously pay for data. In fact we are paying for data even before starting.

It is some of the proposals that are worrying. Some in the ICANN Intellectual Property Constituency (lawyers/brand protection etc) want those accessing the data to be pre-approved and effectively be lawyers investigating intellectual property rights issues. Others want limitations on the data provided. The is some discussion about a field to differentiate natural persons (people) from legal persons (companies) as GDPR does not generally apply to companies.

The scalability aspect:

Ehe... you've just hit the nail in the head. That's the key here.

I'd say that not every startup out there is going to get that key. By looking at your site, can tell you know well about this.

It is a nightmare to get right. Most sites never do the necessary design work at the start and end up trying to retrofit scalability.

Fortunately, this is right down my alley.
Started in 1997 or so with my first search engine... at the end of an 33Kbps leased line (copper wire) internet connection which was costing me an arm an leg back then, it was that expensive.

Four wire analogue modems used to be popular for those lines. The problem then was trying to monetise the content.

Building things that scale is my specialty. And it does require a lot of experience and a lot of work. Especially with optimizing large databases and stuff. But it goes far beyond that. Syncing a swarm of bots and making all working smooth without anything crashing each 10 minutes isn't an easy job.

It sounds like a set of sites rather than one single site.

TBH I have been considering some of the worst applications, where the above is just... piece of cake.

What I always wanted to crack is the area which Ahrefs and Majestic are in, and nowadays Semrush has cracked. But that ain't for the faint hearted. You need not only some serious power, petabytes of disk space and network, and a LOT of funding. Great engineers, large team etc. So this is still nice to look at but probably out of my league.

The guy who started Majestic used to post back on Webmasterworld back in the day. Markus Frind, the guy who started Plenty Of Fish, also posted there and his description of how he set up the site is definitely worth reading even now. He took a completely different approach to design than the large dating sites at the time and beat them. The guy who built ZFbot used to post here on Namepros. Many of the largest websites start with one developer with an idea rather than well resourced teams.

Downsizing a bit, I've been running my network(s) over a few years doing lots of different things and preparing for it. Still doing that. It is a challenge. But it is already up to that. 80% of the tech needed is already done more or less; with codebase in. What is not yet done is putting together everything, and aspects like sales, case use, niches etc. Plus the user interface / layer. But all these are the fun part, right?

The simultaneous users number is always a concern. The key to this is a bit counter-intuitive but it has to do with limiting the user's options.My HTML has been know to make grown web developers cry.

I have zero doubts in the project at this time.

In fact I have been running a couple startups over the past doing various things, for example I had an url shortener that did a few things, such as an A/B rotator test, tracking, blocking some unwanted traffic and providing some stats. It was profitable from the first month; but it was scaling slow so I decided to cut it loose after a bit. There's experience. That's what matters.

There's only one way to get experience and that's by doing it.

There is suppose to be another round of new gTLDs in the next few years and some potential gTLDs are being mentioned already. (coin, wallet etc) and these will grow the numbers of domain names. If they use the heavy discounting model that some of the new gTLDs like .XYZ and others used then the number of deleted domain names will start building up after the second year.

During the Domain Tasting problem in the mid-2000s some of the domain tracking sites crashed because of the millions of domain names being registered and deleted in the five day Add Grace Period. ICANN changed the regulations on this and most of the taster registrars stopped when a restocking fee was added. A few of the main tasting registrars were sued. The only sites that survived were the ones who had built-in scalability. To put it in perspective, approximately 1,000,000,000 .COM domain names were registered and deleted over a few years.

Regards...jmcc

 

[jmcc]

This is the Webmasteworld on running a one person high traffic site:
https://www.webmasterworld.com/website_technology/4496.htm

It is from 2006 and is effectively a Q&A with Markus Frind. What makes this impressive is that he developed and coded it himself.

Regards...jmcc

 

[twiki]

ICANN is heading south. On multiple aspects. But it's all about corporate benefit... what did we expect?

Do no evil, Google. (ICANN)

It is a nightmare to get right. Most sites never do the necessary design work at the start and end up trying to retrofit scalability.

Retrofitting most often doesn't work. With scaling you either 1) have a shitload of money to start from scratch if you f*ed it up, or 2) start well from the beginning and you know what you are doing.

I spent years on the scaling aspect alone. That experience is precious.

It sounds like a set of sites rather than one single site.

There is only one site in this project, really. Dotible.

Everything else is servers running entirely via cron jobs and scripts, and databases connecting all the stuff together. It's all automated and requires close to no maintenance. They feel ... empty, yet busy. Say one supervisor task plants a flag and then various bots go at work depending on the job.

I believe in data-centric, data-driven, disconnected architecture. It's what takes to scale correctly in my opinion. People today over-complicate things a lot due to tech fluff and hype. But of course there is useful new tech as well such as NoSQL and stuff, but I don't need them that much.

The guy who started Majestic used to post back on Webmasterworld back in the day. Markus Frind, the guy who started Plenty Of Fish, also posted there and his description of how he set up the site is definitely worth reading even now. He took a completely different approach to design than the large dating sites at the time and beat them. The guy who built ZFbot used to post here on Namepros. Many of the largest websites start with one developer with an idea rather than well resourced teams.

How about Linus Torwalds? He started by posting about his hobby project... linux... it's just a hobby... it will never grow as much HP-UX or whatnot.

The simultaneous users number is always a concern. The key to this is a bit counter-intuitive but it has to do with limiting the user's options.My HTML has been know to make grown web developers cry.

Don't worry about that. I do have half old GUIs as well and Dotible is nowhere near the fluff needed nowadays.

There will be new interface though but I'm keeping things rather simple for now.

Side note you can improve performance a lot but it depends on the tricks up your sleeve. Sometimes a significant project architecture change is needed (and more servers / higher cost) . Other times you can get away with little.

Dotible tasks can be extremely CPU consuming but I've been working on that. For example the appraiser is nowhere near 500 lines of code or whatever. Took years to refine it. Users want bulk access, well, I need code performance, not just server performance, in order to be able to make a profit.

The guy who started Majestic used to post back on Webmasterworld back in the day. Markus Frind, the guy who started Plenty Of Fish, also posted there and his description of how he set up the site is definitely worth reading even now. He took a completely different approach to design than the large dating sites at the time and beat them. The guy who built ZFbot used to post here on Namepros. Many of the largest websites start with one developer with an idea rather than well resourced teams.

Ah, WMW ... those were some nice times. I felt bad when it basically died. But it was a sign of its times passing.

I used to run some large sites back then, one of mine was top 5 in my country. But over the years sEO changed and I didn't want to go the PBN route, although it's the only way to make SEO performance nowadays.

Final note, domain numbers are increasing anyway, so I guess performance and scale will count much more in upcoming years.

Question, do you fear your model / site is at threat due to the existential threat vs. Whois itself?

 

[jmcc]

ICANN is heading south. On multiple aspects. But it's all about corporate benefit... what did we expect?

It is a multistakeholder model with various constituencies having their input. It has its problems but it could have been a lot worse.

There is only one site in this project, really. Dotible.

As you've outlined, that's the frontend to a lot of other processes.

Everything else is servers running entirely via cron jobs and scripts, and databases connecting all the stuff together. It's all automated and requires close to no maintenance. They feel ... empty, yet busy. Say one supervisor task plants a flag and then various bots go at work depending on the job.

The idea of updating a large site in realtime is unsettling but it is your design and you understand it best.

How about Linus Torwalds? He started by posting about his hobby project... linux... it's just a hobby... it will never grow as much HP-UX or whatnot.

It started on Usenet, I think. Once it became somewhat stable a lot of the Bulletin Board Systems downloaded it from the Internet (fun with FTP and Gopher and slow connections) and it took off from there. There wasn't much of a WWW at that time.

Don't worry about that. I do have half old GUIs as well and Dotible is nowhere near the fluff needed nowadays.

People need data not distractions. Ideally, it might be best to offer a variety of data formats (HTML, CSV, TSV etc).

Ah, WMW ... those were some nice times. I felt bad when it basically died. But it was a sign of its times passing.

Before Google decided to turn to the dark side. Matt Cutts used to post there.

I used to run some large sites back then, one of mine was top 5 in my country. But over the years sEO changed and I didn't want to go the PBN route, although it's the only way to make SEO performance nowadays.

PBNs are remarkably obvious and Google could end them quickly if it was so motivated. They have unnatural social networks.

Final note, domain numbers are increasing anyway, so I guess performance and scale will count much more in upcoming years.

The funny thing is that most of them are not used for websites. The new gTLDs effectively created a lot of one-hit-wonder registrations of randomly generated domain names that were registered once, dropped and never registered again. There are more deleted .COM domain names than there are active .COM domain names. Some registrations were by businesses or individuals. Some where speculative and a lot were junk (Domain Tasting).

Question, do you fear your model / site is at threat due to the existential threat vs. Whois itself?

HosterStats doesn't use WHOIS data. I had to provide WHOIS cover for a registry when it was moving servers/premises a long time ago and it was enough to make that decision obvious.

The idiocy of GDPR was only the start of problems caused by the European Union and te European Commission. There's the NIS2 directive which is even worse and it seems to have been formulatd by people who hadn't a clue about DNS or how it works. The directive wants the operator of every DNS identified.

The ICANN CZDS serves the gTLD zone files now. It makes things a lot easier. I was on the advisory group for that but the problem with the 90 day access renewal was not part of the specification for the CZDS. The provision of zone file access is part of the gTLD registry contracts (some of the registries may deny access on certain grounds). Most ccTLDs do not allow zone file access.

Regards...jmcc

 

[twiki]

@jmcc

I just realized I haven't replied to your last comment here, so here I go.

As you've outlined, that's the frontend to a lot of other processes.

True. But you said sites, well there's only one sites. Anyway this is just about terms used and the meaning we give them. You are right, there are a lot of other processes as well. Some are monitoring, others are queueing and some are doing the cleanup after.

The one thing difficult is to make "everyone" "behave" and stay in their place. Just like crowds they are hard to control.

The idea of updating a large site in realtime is unsettling but it is your design and you understand it best.

I dont' see it unsettling at all. there are mechanisms in place to take care stuff goes well.

Will see later whether a background load-and-switch process is needed. I have that prepared too, but messing with the live workers currently. TBH I never had a DB crash in the past due to this, even on sheer concurrency. It might however delay a bit some larger read jobs from clients, as long as data is still being written to and some workers might be in a little queue over the same particular zone.

People need data not distractions. Ideally, it might be best to offer a variety of data formats (HTML, CSV, TSV etc).

True.

I'll check the site out. Who knows maybe there's something I need too.

Before Google decided to turn to the dark side. Matt Cutts used to post there.

Never liked Cutt Matts, sorry.

Too much BS.

PBNs are remarkably obvious and Google could end them quickly if it was so motivated. They have unnatural social networks.

My only take on this is that they benefit from that somehow. Only deep pocket guys can truly build and maintain a serious PBN. Favoring the little guy? Nah, that doesn't pay so much.

HosterStats doesn't use WHOIS data.

That's good.

Hmm I just realized using Whois data, and especially further selling / providing Whois data, without the approval of the registrar, even if obtained from a public Whois server, might be grounds for some serious lawsuit.

I'm probably going to stay out of it. For what I need, it's more or less okay without Whois.

Going to shoot you a DM with some question BTW.

The idiocy of GDPR was only the start of problems caused by the European Union and te European Commission. There's the NIS2 directive which is even worse and it seems to have been formulatd by people who hadn't a clue about DNS or how it works. The directive wants the operator of every DNS identified.

I haven't even dared yet to search / look at the NIS2 directive. Has it been issued already?

The EU is going south btw - on so many levels. I'm in the EU so I do know this well. They only aggravate me, really. I spent countless hours reading the GDPR and working with our lawyers as theres' so much stuff there that doesn't add up. In the end, it all went clear. I would sum everything in just one word: bollocks.

The intention is good if you ask me, at least in principle. There's need for better data protection; but this is the format they came up with? Those folks are only lawyers and politicians; and they have no clue whatsoever as to how tech works. I doubt they even asked the tech people a thing. They just decided: "Do this, I don't care how" and the result is NOT better data protection, but rather hindering and damaging serious business and services that important things might depend on.