Hacker News new | ask | show | jobs
by gwu78 4490 days ago
"We peaked at 12."

Peaked. And that probably includes the sysadmin who was required to watch it.

Where are the articles on the new ridiculous TLD's?

A while back the IP address for the FTP copy of the root.zone changed.

And sure enough, the file is now full of crap like .buzz, .house and .kitchen

I cannot even read through the whole zone anymore. It's too long.

There are some gems in there though. And some fool paid $185,000+ for each one.

I have been running my own root for years and this is why.

Snip, snip. No more .buzz

Very easy to set up up your own custom root and to filter out the crap TLD's. But, like with the ceremony in this article, some folks think that ICANN has some sort of "authority" on how people use domain names.

Whole .com zone (=public information) fits on a USB stick.

And the HOSTS file remains as a failsafe, if you have to use someone else's resolver.

And most of the entries in the com.zone are garbage anyway: parked names with ads.

Imagine how many different domains the average user will visit in their lifetime. It is but a small fraction of all the names registered.

But let's pretend ICANN is relevant.

God help us if ICANN should cease to exist.

1 comments

How do you manage your own root?
1. Get copy of the file "root.zone" from ftp.internic.net

2. Load it into tinydns or nsd. I have a sed script that translates BIND format into tinydns format, but if you search you will find someone has written one in C.

3. Point your resolver at your root.

4. Create or delete TLD's at will, not to mention many other benefits.

Running your own DNS gives lots of control. Most malicious or deceptive practices that tarnish the internet rely on DNS. When you control your own, you can neutralize a very large percentage of it.

Redirecting .apple.com to your own httpd will show you just how bad this company has gotten.

You can also redirect ad servers like .doubleclick.net and voila, you will have free apps with NO ADS.

Redirecting .apple.com to your own httpd will show you just how bad this company has gotten.

Care to expand on that?

I'm not going to rant about how Apple products make gratuitous network connections to remote computers for questionable reasons. Nor the requests that many AppStore apps send out over the open internet without telling you, or how poor Apple's forced software has gotten in general.

That's why I've presented you with the experiment.

If you think you might care about such things, try it yourself and draw your own conclusions.

If you use iOS, you might need this, just to get on your own home LAN:

/test/library/success.html <HTML><HEAD><TITLE>Success</TITLE></HEAD></HTML>