Skip to Content.
Sympa Menu

discuss - [opennic-discuss] Fwd: server setup

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

[opennic-discuss] Fwd: server setup


Chronological Thread 
  • From: Dale <dweide9 AT aim.com>
  • To: discuss AT lists.opennicproject.org
  • Subject: [opennic-discuss] Fwd: server setup
  • Date: Sat, 28 Jan 2012 12:20:04 -0500 (EST)
  • List-archive: <http://lists.darkdna.net/pipermail/discuss>
  • List-id: <discuss.lists.opennicproject.org>




Hi all,
I'm hoping someone can help me help my ISP. As per earlier directions from
Amrit, I contacted my ISP & asked them to set up an rDNS for my home
webserver. Below you'll note that the tech guy requested info for the .free
TLD Tier1 server. I gave this to him but is this the info he really needs? As
you can see below, he was unable to set up the rDNS for me using that server
info. Can anyone tell what he was doing wrong? I think Amrit felt this was
the issue after seeing the nslookup results that are far below.
I just switched to a small local ISP, who gave me a static ip & are quite
willing to help me (though they may be lacking the technical know-how), so
the answer wouldn't be to switch my ISP again.


Dale


-----Original Message-----
From: David T <davidterc AT napanet.net>
To: 'Dale' <dweide9 AT aim.com>
Sent: Fri, Jan 27, 2012 2:55 pm
Subject: RE: server setup



The system won’t allow us to enter this in:

The name 202.83.95.229 can not be assigned to 50.0.97.146 because
202.83.95.229 currently points to 202.83.95.229. 202.83.95.229 must point to
50.0.97.146.

We don’t have anyone here who would be able to setup something like this for
you, you would have to look elsewhere unfortunately for guidance on the
issue.


David Tercovich
Systems Administrator
Napanet Internet Services
947 Lincoln Ave. Napa, CA 94558
707-299-1000 x103

From: Dale [mailto:dweide9 AT aim.com]
Sent: Friday, January 27, 2012 12:05 PM
To: davidterc AT napanet.net
Subject: Re: server setup


Hi David,

If the rDNS needs to be the .free TLD Tier1 server at opennic, then yes that
would be correct.
Is this the missing link that will allow surfers to find my server when they
try to go to freespeech.free? Also, if things are set up properly on your end
but people still can't connect to freespeech.free, could I pay a service fee
to have someone troubleshoot my server settings?



Dale





-----Original Message-----
From: David T <davidterc AT napanet.net>
To: 'Dale' <dweide9 AT aim.com>
Sent: Fri, Jan 27, 2012 9:38 am
Subject: RE: server setup


So for clarification, you would like me to set your rDNS to 202.83.95.229
correct?







David Tercovich

Systems Administrator

Napanet Internet Services

947 Lincoln Ave. Napa, CA 94558

707-299-1000 x103



From: Dale [mailto:dweide9 AT aim.com]
Sent: Thursday, January 19, 2012 3:36 PM
To: support AT napanet.net
Subject: Fwd: server setup




Tech support,


First I would like to say thanks to the tech support guy who helped me on
Tuesday. I think his name was David, but I owe him a beer anyway.


Per David's request, this e-mail's purpose is to give you the Tier1 servers
for opennic.glue, so that people trying to reach my home webserver at
freespeech.free can find it. Actually I only see one server for the .free
TLD, which is called ns21, is at ip address 202.83.95.229, & the admin is
Julian De Marchi. If you really need a secondary, I would go with server ns5
at 128.177.28.254. (and in case you need it, my static ip is 50.0.97.146) I
got this info from this address: wiki.opennicproject.org/Tier1
Let me know if you need anything else (nslookup & system file info is below),


Dale Weide


# 225-7654





-----Original Message-----
From: Amrit Panesar <apanesar AT 4195tech.com>
To: discuss <discuss AT lists.opennicproject.org>
Sent: Mon, Jan 16, 2012 9:34 pm
Subject: Re: [opennic-discuss] server setup

It would appear that your reverse host record is controlled by your ISP. You
have to ask them to give you a RDNS ((and subsequently a static ip). As for
your forward lookup zone, try
running 'bind-checkzone <zone name> <zone file>' that usually shows any zone
configuration syntax errors that may be lingering. (also bind-checkconf is
also
a very valuable tool for checking your bind.conf and included files). And if
all
else fails, try enabling logging (specifically all the logging channels,
including the debug) and see what bind spits out when it starts up

Thanks

--Amrit

Sent from my iPhone

On Jan 16, 2012, at 21:10, Dale <dweide9 AT aim.com> wrote:

> Thank you for the warm responses about helping.
> Okay, here we go. As I had mentioned earlier, I can access my web server by
> ip
but not name. Below is info from various files. Please let me know what the
&$@$!#* I'm doing wrong. My server ip address is 50.0.97.146, I'm using a
local
isp but looks like they utilize sonic.net & dsltransport.net If I do nslookup
of
my ip from another computer I get:
>
> gnomad@dales-hp-laptop:~$ nslookup 50.0.97.146
> Server: 74.207.247.4
> Address: 74.207.247.4#53
>
> Non-authoritative answer:
> 146.97.0.50.in-addr.arpa name = 50-0-97-146.static.dsltransport.net.
>
> Authoritative answers can be found from:
> 0.50.in-addr.arpa nameserver = A.AUTH-NS.SONIC.net.
> 0.50.in-addr.arpa nameserver = B.AUTH-NS.SONIC.net.
> 0.50.in-addr.arpa nameserver = C.AUTH-NS.SONIC.net.
> A.AUTH-NS.SONIC.net internet address = 209.204.159.20
> A.AUTH-NS.SONIC.net has AAAA address 2001:5a8:0:3::1
> B.AUTH-NS.SONIC.net internet address = 184.173.92.18
> B.AUTH-NS.SONIC.net has AAAA address 2607:f0d0:1102:f::2
> C.AUTH-NS.SONIC.net internet address = 69.9.186.104
> C.AUTH-NS.SONIC.net has AAAA address 2001:48c8:1:1::2








Archive powered by MHonArc 2.6.19.

Top of Page