Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Name server failure? - also Hardware Requirements?

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Name server failure? - also Hardware Requirements?


Chronological Thread 
  • From: "Jerry Pipes" <domains AT snewpy.com>
  • To: <discuss AT lists.opennicproject.org>
  • Subject: Re: [opennic-discuss] Name server failure? - also Hardware Requirements?
  • Date: Sun, 4 Jan 2015 05:33:52 -0600

Hi Brian,

Thanks for the response. See my comments below.

----- Original Message ----- From: "Brian Koontz" <brian AT opennicproject.org>
To: <discuss AT lists.opennicproject.org>
Sent: Saturday, January 03, 2015 9:32 PM
Subject: Re: [opennic-discuss] Name server failure? - also Hardware Requirements?
Both servers check out fine. It sounds to me like your ISP might be
redirecting port 53 access (Comcast, by chance?), and that it took some
time for your DNS changes to propagate through to the other computers (esp.
if done at the router). Browsers cache their DNS settings for quite a
while.

I've since reconfigured my PC alone to use the OpenNIC servers, and everything seems to be working okay.

A RPi would be great for a local caching server! If you're interested in
running a Tier 2, you'd most likely want a *nix-based VM hosted elsewhere
to do this.

Is this how most people do it? At some point, I'm planning to start my own TLD, so I would probably use the same hardware for both, right?

Processing and bandwidth requirements are modest. The
important thing is that you will want to run whitelisting and some firewall
rules that will throttle down the connection considerably in the event of a
DDOS attack.

I'm doing this as a learning experience, so I think I'd enjoy setting up my own server and configuring everything. My *nix skills are a little rusty, but I think I could manage. What kind of hardware are you running for .gopher?

Jerry



Archive powered by MHonArc 2.6.19.

Top of Page