It’s not a “bug” it’s a “process to delay a domain from dropping” – Part III

Continuing on from our last article that outlined how used “technical trickery” to stop a domain name from dropping, then handed over their own Terrific Server Connection to a friend with a direct commercial relationship to win the domain name back for himself.

Today Domainer would like to clear up exactly what this “bug” is and ask you to consider that it isn’t really a “bug” at all, as are claiming.

Rather than a bug, we believe it’s really a process to delay a domain from dropping, or PDDD for short.

And 100% used this power to stop from dropping and they STILL HAVE THIS POWER TODAY.

Here’s how Drop can perform the “process to delay a domain from dropping” whenever they like;

Step 1. They find a domain name on the drop list that they “don’t want to drop”.

Step 2. They create “GLUE RECORDS” – A glue record is simply the association of a hostname (nameserver, or DNS ) with an IP address at the registry.

Step 3. They register a new domain name (eg – and point the DNS records directly to the domain name they want to stop from dropping, to create a DEPENDENCY.

Hey Presto! They just deliberately stopped a domain name from dropping.

And it appears they have known about this PDDD since July 1st, 2018 and have NEVER told Netfleet.

How does this help

In a multiple of ways.

Firstly, it gives them time to get all their “ducks in a row”, particularly their server connections.

Secondly, Anthony was involved in building the Netfleet Drop-Catching system, back in the day, so we believe he may have knowledge that Netfleet are “less successful” in catching domain names if they are moved to the following day.

The way we know for a fact that did this in the dying hours of dropping is, if the “Glue Records” and “DNS Dependency” had already been engaged for this domain name over a week ago, IT WOULD NEVER HAVE APPEARED ON THE DROP LIST IN THE FIRST PLACE.

Because, this is how Afilias have the Registry System configured at this moment!

Afilias seem to have created a rule that states: if a domain name has “glue records” at the Registry and “DNS Dependency”, then, DO NOT LIST THE DOMAIN NAME ON THE DROPS.

This was never the case with the AusRegistry system.

What did was a deliberate act to stop from dropping. Then, the Terrific Server Connection that have been using for ages, was suddenly handed over to a friend with a commercial relationship at the last minute to BEAT one of their own clients.

Sound like a fair company?

Sound like a fair system?

How many domain names have been doing this with, since July 1st, 2018?

4 thoughts on “It’s not a “bug” it’s a “process to delay a domain from dropping” – Part III

  • May 6, 2019 at 2:53 pm


    David Warmuz has asked we make a clarification:

    He wrote:

    “you should also clarify that this can only be done on domains that are under your registrar, and not imply that this can be done on any name we like.”

    Domainer can not confirm this is true, but this may be the case. Perhaps another Registrar operator can confirm?

    David also wrote to me today:

    “What baffles me is, how come you did not go crazy about the that was also delayed in the same way, but not by Drop, but by our competitors??? Is it because we managed to catch that name for you that you are fine with it??? Rather hypocritical if so.”

    No hypocrisy. was a different situation.

    For starters: I bid on that domain and was the WINNER on both platforms on Day 1. But it didn’t drop. Someone else won the domain a few days later, and I had to approach them and ask to buy it privately. Lucky for me they agreed to let me buy it. Drop did not manage to catch the domain name for me. And in no way do I believe a competitor performed the sneaky “PDDD” system on

    Because… was in the “expired list” and then it changed to “Policy Delete”, which is why we (the Domainer Team) think it didn’t drop on the first day. Not the same as

    4 people like this.
  • May 6, 2019 at 3:21 pm

    Got to give it to David Warmuz. He has chutzpah. He now seeks to divert from the real issue of Terrific catching for the husband of one of their dropcatching connections. The same bloke that forgot to renew it. No mention that Anthony Peake was a Director of that company. Perhaps David could answer the question he avoided on DNTrade. Has Jonathan Horne been acting as a shadow director of Terrific Pty Ltd?

    6 people like this.
  • May 6, 2019 at 9:55 pm

    It’s been 7 days since this issue came to light and auDA hasn’t bothered to publicly acknowledged this issue or provide any assurances to the internet community about resolving this serious matter.

    2 people like this.
  • May 9, 2019 at 1:23 pm

    It seems there’s lots of people saying things without consulting lawyers (or perhaps Police) first.
    Either one or more companies who may have suffered financial loss through the alleged actions of will be taking legal action against Drop or Drop will be taking action against for making a false and defamatory claim against Drop (or both).
    I see the actions alleged (notice I am saying alleged) to have been taken by Drop (with possible involvement of other parties) is effectively Fraud.
    Further, I think the bidding systems used by Drop and Netfleet and any other companies auctioning dropped domains in the future need to provide a transparent process where bidders/bids and outcomes are publicly visible. The ridiculous exponential bidding increments should be replaced as well.

    2 people like this.

Comments are closed.