Discuss mailing list

[Dale <dweide9 AT aim.com>]

Hi Amrit,
I guess I was wrongly under the assumption that bind was essential in order 
for a webserver to resolve it's domain name. That's why I already have bind9 
running on my server, it is set as master of my domain, & it has the 
appropriate file with a reverse look up zone & a Pointer Record (PTR), but 
freespeech.free is still unreachable even with all this. So I wrote my ISP & 
said in order for my domain name to work, it appears essential that they 
create a PTR. FYI, here is what my file looks like, which I'm assuming is 
somewhat similar to what my ISP will need to create (I know it should have 2 
name servers listed but bind threw an error, which resolved when I removed 
it):
> ; BIND reverse data file for my local interface
> ;
> $TTL    86400
> @       IN      SOA     ns1.freespeech.free. dweide9.netscape.net. (
>                             2          ; Serial
>                         28800          ; Refresh
>                          7200          ; Retry
>                        604800          ; Expire
>                         86400 )        ; Negative Cache TTL
> ;
> @       IN      NS      ns1.
> @       IN      A       202.83.95.228
> 10    IN    PTR    ns1.freespeech.free.
Thanks again for your help,

Dale




-----Original Message-----
From: Amrit Panesar <apanesar AT 4195tech.com>
To: discuss <discuss AT lists.opennicproject.org>
Sent: Sat, Jan 28, 2012 9:45 am
Subject: Re: [opennic-discuss] Fwd: server setup


The way I can see this playing out is like this:

Essentially you need to run a Bind9 server. This DNS server will be 
authoritative (master) for your opennic domain(s). Generally, your ISP is 
supposed to set the Pointer Record (PTR) on their own, any time you need to 
change your rDNS, you're supposed to go through them. However, I think 
they're 
trying to delegate (using an NS record) the rDNS to the Tier1 server, this is 
not correct. Any Tier1 servers are only authoritative for OpenNIC zones. So, 
as 
per your rDNS, you either need to make a reverse look up zone with a PTR 
record 
for your IP OR (in what I believe is the proper way to do this) have your ISP 
set the PTR on their end.

Just to reiterate, even if your ISP doesn't resolve OpenNIC zones (though you 
should definitely urge them to!), they can still set an rDNS for your ip with 
an 
OpenNIC domain.

Good Luck!

--Amrit

Sent from my iPhone

On Jan 28, 2012, at 9:20, Dale <dweide9 AT aim.com> wrote:

> 
> 
> 
> 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