Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] DNS Server does not resolve OpenNIC TLDs

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] DNS Server does not resolve OpenNIC TLDs


Chronological Thread 
  • From: Brian Koontz <brian AT opennicproject.org>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] DNS Server does not resolve OpenNIC TLDs
  • Date: Thu, 17 May 2012 22:13:28 -0500

On Thu, May 17, 2012 at 08:57:11PM +0200, Gandalf wrote:
> Here's the result:
>
> ------------------------------------------------------------------------------------------------
> C:\Users\ntb>nslookup grep.geek
> Server: 19.blockaid.me
> Address: 178.21.23.150
>
> DNS request timed out.
> timeout was 2 seconds.
> *** 19.blockaid.me can't find grep.geek: Non-existent domain
>
> C:\Users\ntb>nslookup grep.geek 178.21.23.150
> Server: 19.blockaid.me
> Address: 178.21.23.150
>
> *** 19.blockaid.me can't find grep.geek: Non-existent domain
> -------------------------------------------------------------------------------------------------------

First off, I would recommend installing dig (might have to use cygwin,
don't know for sure). nslookup is notoriously flaky.

Also, running dig with the +trace flag might be helpful.

Your DNS appears to be getting redirected. Here are my results:

brian@turquoise <10:07 PM> 502$ dig @178.21.23.150 grep.geek

; <<>> DiG 9.3.0 <<>> @178.21.23.150 grep.geek
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52727
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;grep.geek. IN A

;; ANSWER SECTION:
grep.geek. 60 IN A 216.87.84.210

;; Query time: 345 msec
;; SERVER: 178.21.23.150#53(178.21.23.150)
;; WHEN: Thu May 17 22:08:06 2012
;; MSG SIZE rcvd: 43

--Brian

--
OpenNIC (the sequel) co-founder and wikimaster
IRC: Freenode.net channel #opennic



Archive powered by MHonArc 2.6.19.

Top of Page