Discuss mailing list

[Christopher <weblionx AT gmail.com>]

Martin: I'm not entirely sure on this, but it seems like this: You
have NS servers set in your .free records. This means clients will ask
those name servers for the IP address. You want to set your A record
on your host's nameservers, or get rid of the NS entries.

On Thu, Jan 5, 2012 at 9:56 AM, Maximi89 <maximi89 AT gmail.com> wrote:
> 2012/1/5 Peter Green <peter AT greenpete.org>
>
>> I run two servers and neither use OpenNIC resolvers yet one of them
>> happily runs greenpete.free
>>
>> I wonder why/how?
>>
>> Peter
>>
>> Wanged from my Kaiser by a mischievous pixie!
>>
>> Hospedaje Web y Servidores Dedicados <ventas AT dedicados.com.mx> wrote:
>>
>> >If 000webhost.com dont have opennic ips as resolvers, at least 2, your
>> domains never going to work.
>> >
>> >Because 000 cant see them. Even if you have installed the ips correctly
>> on your pc.
>> >
>> >
>>
> Time ago i was with www.maximi89.ing working on them and various domains
> more... but after 30 days it stopped working due the webhosting can't see
> it... but it should work...
>
>> >
>> >
>> >--
>> >Ing. Alejandro M.
>> >-----------------------
>> >Hospedaje Web y Servidores Dedicados
>> >http://www.dedicados.com.mx
>> >-----------------------
>> >ventas AT dedicados.com.mx
>> >-----------------------
>> >
>> >-----Original Message-----
>> >From: subhuman <discipline AT gmx.net>
>> >Sender: discuss-bounces AT lists.opennicproject.org
>> >Date: Thu, 5 Jan 2012 15:06:27
>> >To: <discuss AT lists.opennicproject.org>
>> >Reply-To: discuss AT lists.opennicproject.org
>> >Subject: [opennic-discuss] Domains not accessible
>> >
>> >My apologies in advance for revivifying this ancient topic once again.
>> >But I still seem to be too dull. :(
>> >
>> >The problem is that I own two opennic domains on 000webhost.com - and
>> >that whatever I do, I don't get them to work. The information I have
>> >look somewhat contradictory to me, hence I ask for your guidance:
>> >
>> >In (relatively) short:
>> >
>> >1.) 000webhost.com sent me the IPs for the servers on which they host
>> >my domains. They are the ones with which I updated the reg.for.free A
>> >records.
>> >
>> >2.) 000webhost.com names nameservers I should use: "Nameserver
>> >details (only if you host your own domain)" - which I don't. I want the
>> >domains be hosted on 000.webhost.com servers. If I'm not totally dumb
>> >(and I'm probably not to exclude that possibility) this means that I
>> >may NOT use their nameservers.
>> >
>> >3.) 000webhost.com then tells me that "You can also point your domain
>> >("A" DNS record) to IP 31.170.163.38" - which I don't understand at
>> >all. What the heck am I to do with this IP?
>> >
>> >4.) 000webhost then complains that "Your domain is not yet pointing our
>> >server, so services such as FTP, Website Builder or File Manager may
>> >not work. You need to update nameservers to ns01.000webhost.com,
>> >ns02.000webhost.com for your domain." The first statement is of course
>> >true, but the directive that follows is contradictory, isn't it? I
>> >mean, I have to update the nameservers ONLY if I'm going to host the
>> >domains myself. True?
>> >
>> >5.) As mentioned in 1.) the IPs in the following A records came fresh
>> >from 000webhost. I edited the records shortly after Xmas. However,
>> >nothing seems to be dripping through the DNS hierarchy. some.null still
>> >points to that ominous 64.xxx IP (and I have no idea when and why I
>> >might have entered that), and I get a ServFail when asking for minus.null.
>> >
>> >What am I doing wrong? Or is it not my fault anyway? I can't tell, can
>> >anyone else please? You find further data below.
>> >
>> >--Martin
>> >
>> >P.S. Happy New Year, btw.
>> >
>> >
>> >Domain 1: some.null
>> >============
>> >The reg.for.free records are:
>> >registered with reg.for.free, records are:
>> >
>> >Record         Type            Data                    Aux
>> TTL             Active  Edit
>> >                       A                       31.170.160.84   0
>>       86400   Y
>> >                       NS                      ns1.some.null.   0
>>      86400   Y
>> >                       NS                      ns2.some.null.   0
>>      86400   Y
>> >ns1.some.null.         A                       202.83.95.228    0
>>      86400   Y
>> >ns2.some.null.         A                       119.31.230.42    0
>>      86400   Y
>> >
>> >I updated the IP for the A record more than a week ago, however, it
>> >doesn't get propagated through the server hierarchy. This is what dig
>> tells me:
>> >
>> >
>> >~$ dig some.null
>> >
>> >; <<>> DiG 9.7.3 <<>> some.null
>> >;; global options: +cmd
>> >;; Got answer:
>> >;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61812
>> >;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>> >
>> >;; QUESTION SECTION:
>> >;some.null.                     IN      A
>> >
>> >;; ANSWER SECTION:
>> >some.null.              43200   IN      A       64.191.56.21
>> >
>> >;; Query time: 342 msec
>> >;; SERVER: 83.223.73.116#53(83.223.73.116)
>> >;; WHEN: Thu Jan  5 14:37:47 2012
>> >;; MSG SIZE  rcvd: 43
>> >
>> >and
>> >:~$ dig some.null SOA
>> >
>> >; <<>> DiG 9.7.3 <<>> some.null SOA
>> >;; global options: +cmd
>> >;; Got answer:
>> >;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63154
>> >;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>> >
>> >;; QUESTION SECTION:
>> >;some.null.                     IN      SOA
>> >
>> >;; ANSWER SECTION:
>> >some.null.              41244   IN      SOA     ns1.some.null.
>> sub_human.web.de. 2011010801 28800 7200 604800 86400
>> >
>> >;; Query time: 10 msec
>> >;; SERVER: 83.223.73.116#53(83.223.73.116)
>> >;; WHEN: Thu Jan  5 14:38:42 2012
>> >;; MSG SIZE  rcvd: 83
>> >
>> >And, funny enough (to me):
>> >~$ dig @ns2.opennic.glue some.null
>> >
>> >; <<>> DiG 9.7.3 <<>> @ns2.opennic.glue some.null
>> >; (2 servers found)
>> >;; global options: +cmd
>> >;; Got answer:
>> >;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10265
>> >;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
>> >;; WARNING: recursion requested but not available
>> >
>> >;; QUESTION SECTION:
>> >;some.null.                     IN      A
>> >
>> >;; AUTHORITY SECTION:
>> >some.null.              18000   IN      NS      ns2.nic.free.
>> >some.null.              18000   IN      NS      ns1.nic.free.
>> >
>> >;; Query time: 198 msec
>> >;; SERVER: 216.87.84.210#53(216.87.84.210)
>> >;; WHEN: Thu Jan  5 14:43:20 2012
>> >;; MSG SIZE  rcvd: 71
>> >
>> >
>> >Domain 2: minus.null
>> >============
>> >records at reg.for.free:
>> >Record         Type    Data                    Aux     TTL
>> Active  Edit
>> >                       A               31.170.160.78  0        86400    Y
>> >                       NS              ns1.minus.null.         0
>> 86400    Y
>> >                       NS              ns2.minus.null.         0
>> 86400    Y
>> > ns1.minus.null.  A            202.83.95.228  0        86400    Y
>> > ns2.minus.null.  A            119.31.230.42  0        86400    Y
>> >
>> >~$ dig minus.null
>> >
>> >; <<>> DiG 9.7.3 <<>> minus.null
>> >;; global options: +cmd
>> >;; Got answer:
>> >;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 63047
>> >;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>> >
>> >;; QUESTION SECTION:
>> >;minus.null.                    IN      A
>> >
>> >;; Query time: 715 msec
>> >;; SERVER: 83.223.73.116#53(83.223.73.116)
>> >;; WHEN: Thu Jan  5 14:42:47 2012
>> >;; MSG SIZE  rcvd: 28
>> >
>> >:~$ dig @ns2.opennic.glue minus.null
>> >
>> >; <<>> DiG 9.7.3 <<>> @ns2.opennic.glue minus.null
>> >; (2 servers found)
>> >;; global options: +cmd
>> >;; Got answer:
>> >;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3693
>> >;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
>> >;; WARNING: recursion requested but not available
>> >
>> >;; QUESTION SECTION:
>> >;minus.null.                    IN      A
>> >
>> >;; AUTHORITY SECTION:
>> >minus.null.             18000   IN      NS      ns1.nic.free.
>> >minus.null.             18000   IN      NS      ns2.nic.free.
>> >
>> >;; Query time: 202 msec
>> >;; SERVER: 216.87.84.210#53(216.87.84.210)
>> >;; WHEN: Thu Jan  5 14:43:14 2012
>> >;; MSG SIZE  rcvd: 72
>> >_______________________________________________
>> >discuss mailing list
>> >discuss AT lists.opennicproject.org
>> >http://lists.darkdna.net/mailman/listinfo/discuss
>> >
>> >You may unsubscribe by emailing
>> discuss-unsubscribe AT lists.opennicproject.org.
>> >_______________________________________________
>> >discuss mailing list
>> >discuss AT lists.opennicproject.org
>> >http://lists.darkdna.net/mailman/listinfo/discuss
>> >
>> >You may unsubscribe by emailing
>> discuss-unsubscribe AT lists.opennicproject.org.
>> >
>> _______________________________________________
>> discuss mailing list
>> discuss AT lists.opennicproject.org
>> http://lists.darkdna.net/mailman/listinfo/discuss
>>
>> You may unsubscribe by emailing
>> discuss-unsubscribe AT lists.opennicproject.org.
>>
>
>
>
> --
> Maximiliano Augusto Castañón Araneda
> Santiago, Chile
> Linux user # 394821
>
> Skype: maximi89
> MSN: maximi89 AT gmail.com
> XMPP/Jabber: maximi89 AT gmail.com
>
> _______________________________________________
> discuss mailing list
> discuss AT lists.opennicproject.org
> http://lists.darkdna.net/mailman/listinfo/discuss
>
> You may unsubscribe by emailing 
> discuss-unsubscribe AT lists.opennicproject.org.