nslookup -d www.barriq.com 8.8.8.8 no resolving

84 views
Skip to first unread message

BARRIQ

unread,
Sep 22, 2010, 6:51:46 PM9/22/10
to public-dns-discuss, sum...@tigertext.com
Resolving fine on 4.2.2.1...but not 8.8.8.8


C:\USERS\SWHITE~1>nslookup -debug barriq.com 8.8.8.8
------------
Got answer:
HEADER:
opcode = QUERY, id = 1, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0,
additional = 0

QUESTIONS:
8.8.8.8.in-addr.arpa, type = PTR, class = IN
ANSWERS:
-> 8.8.8.8.in-addr.arpa
name = google-public-dns-a.google.com
ttl = 85962 (23 hours 52 mins 42 secs)

------------
Server: google-public-dns-a.google.com
Address: 8.8.8.8

------------
Got answer:
HEADER:
opcode = QUERY, id = 2, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
barriq.com.corp.slingshotlabs.com, type = A, class = IN
AUTHORITY RECORDS:
-> slingshotlabs.com
ttl = 85967 (23 hours 52 mins 47 secs)
primary name server = ns33.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2010080202
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 3, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
barriq.com.corp.slingshotlabs.com, type = AAAA, class = IN
AUTHORITY RECORDS:
-> slingshotlabs.com
ttl = 85967 (23 hours 52 mins 47 secs)
primary name server = ns33.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2010080202
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 4, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
barriq.com.slingshotlabs.com, type = A, class = IN
AUTHORITY RECORDS:
-> slingshotlabs.com
ttl = 85967 (23 hours 52 mins 47 secs)
primary name server = ns33.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2010080202
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 5, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
barriq.com.slingshotlabs.com, type = AAAA, class = IN
AUTHORITY RECORDS:
-> slingshotlabs.com
ttl = 85967 (23 hours 52 mins 47 secs)
primary name server = ns33.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2010080202
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 6, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 2, authority records = 0,
additional = 0

QUESTIONS:
barriq.com, type = A, class = IN
ANSWERS:
-> barriq.com
internet address = 216.104.161.202
ttl = 3088 (51 mins 28 secs)
-> barriq.com
internet address = 216.104.161.102
ttl = 3088 (51 mins 28 secs)

------------
Non-authoritative answer:
------------
Got answer:
HEADER:
opcode = QUERY, id = 7, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
barriq.com, type = AAAA, class = IN
AUTHORITY RECORDS:
-> barriq.com
ttl = 3167 (52 mins 47 secs)
primary name server = ns1.domaindiscover.com
responsible mail addr = hostmaster.tierra.net
serial = 2010091503
refresh = 7200 (2 hours)
retry = 1800 (30 mins)
expire = 604800 (7 days)
default TTL = 28800 (8 hours)

------------
Name: barriq.com
Addresses: 216.104.161.202
216.104.161.102


C:\USERS\SWHITE~1>nslookup -d www.barriq.com 8.8.8.8
------------
Got answer:
HEADER:
opcode = QUERY, id = 1, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0,
additional = 0

QUESTIONS:
8.8.8.8.in-addr.arpa, type = PTR, class = IN
ANSWERS:
-> 8.8.8.8.in-addr.arpa
name = google-public-dns-a.google.com
ttl = 85859 (23 hours 50 mins 59 secs)

------------
Server: google-public-dns-a.google.com
Address: 8.8.8.8

------------
Got answer:
HEADER:
opcode = QUERY, id = 2, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
www.barriq.com.corp.slingshotlabs.com, type = A, class = IN
AUTHORITY RECORDS:
-> slingshotlabs.com
ttl = 85873 (23 hours 51 mins 13 secs)
primary name server = ns33.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2010080202
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 3, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
www.barriq.com.corp.slingshotlabs.com, type = AAAA, class = IN
AUTHORITY RECORDS:
-> slingshotlabs.com
ttl = 85873 (23 hours 51 mins 13 secs)
primary name server = ns33.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2010080202
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 4, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
www.barriq.com.slingshotlabs.com, type = A, class = IN
AUTHORITY RECORDS:
-> slingshotlabs.com
ttl = 85873 (23 hours 51 mins 13 secs)
primary name server = ns33.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2010080202
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 5, rcode = NXDOMAIN
header flags: response, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1,
additional = 0

QUESTIONS:
www.barriq.com.slingshotlabs.com, type = AAAA, class = IN
AUTHORITY RECORDS:
-> slingshotlabs.com
ttl = 85874 (23 hours 51 mins 14 secs)
primary name server = ns33.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2010080202
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

------------
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
*** Request to google-public-dns-a.google.com timed-out

Paul S. R. Chisholm

unread,
Sep 23, 2010, 10:34:10 AM9/23/10
to public-dn...@googlegroups.com, se...@tigertext.com, sum...@tigertext.com
Sean, sorry you're having problems; thanks for the diagnostic information.

I can confirm that 4.2.2.1 is resolving www.barriq.com, but I'm not
sure why or how. I think it's got old cached delegation information,
which is helping for the moment. When that delegation information
expires, 4.2.2.1 will also be unable to resolve www.barriq.com.

The current delegation information (according to all the .com servers) is:

;; AUTHORITY SECTION:
barriq.com. 172800 IN NS ns1.domaindiscover.com.
barriq.com. 172800 IN NS ns2.domaindiscover.com.

;; ADDITIONAL SECTION:
ns1.domaindiscover.com. 172800 IN A 216.104.162.3
ns2.domaindiscover.com. 172800 IN A 216.104.163.3

Unfortunately, both of those authoritative nameservers are having problems:

$ dig @216.104.162.3 +noquestion +nocmd +nostats +norecurse www.barriq.com
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
;; Connection to 216.104.162.3#53(216.104.162.3) for www.barriq.com
failed: connection refused.

$ dig @216.104.163.3 +noquestion +nocmd +nostats +norecurse www.barriq.com
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
;; Connection to 216.104.163.3#53(216.104.163.3) for www.barriq.com
failed: connection refused.

OpenDNS is also having trouble resolving www.barriq.com:

$ host $(dig @resolver1.opendns.com +short www.barriq.com)
132.66.215.67.in-addr.arpa domain name pointer servfail.guide.opendns.com.
132.66.215.67.in-addr.arpa domain name pointer hit-servfail.opendns.com.

(That means: OpenDNS gives you an answer, but the answer is the
address of the host that handles resolution failures.)

If you operate barriq.com, please contact your hosting service and
report this problem

Hope this helps. --PSRC

P.S.: If you're wondering: The references in your output to
"barriq.com.corp.slingshotlabs.com" are an artifact of the list of
domains your PC tries.

Sean Whiteley

unread,
Sep 23, 2010, 5:16:27 PM9/23/10
to Paul S. R. Chisholm, public-dn...@googlegroups.com, Sumeet Bhatia
Hey Paul!

Domain Discover updated their servers and it should be working now. How
long does it take for Google's servers to update?

Thanks for all your help.

Sean

Sean Whiteley
TigerText
1310 Montana Ave
Second Floor
Santa Monica, CA 90403
310.363.0565 x224
310.710.5288 cell
310.622.4526 fax
se...@tigertext.com
Delete Your Text Messages Free
TigerText Username ‘sean’

Paul S. R. Chisholm

unread,
Sep 24, 2010, 11:26:22 AM9/24/10
to Sean Whiteley, public-dn...@googlegroups.com, Sumeet Bhatia
Sean, what are you seeing that's different? I'm still seeing the same
delegation information from the .com nameservers, and the same
timeouts from the authoritative nameservers. --PSRC

Paul S. R. Chisholm

unread,
Sep 24, 2010, 2:58:39 PM9/24/10
to public-dn...@googlegroups.com, Sean Whiteley, Sumeet Bhatia
FYI: After better understanding the exact misbehavior of the
authoritative nameservers, I was able to make a tweak to Google Public
DNS so it can now resolve www.barriq.com.

This tweak will *only* help Google Public DNS users. Other DNS
services may still have trouble resolving www.barriq.com; at least one
that I know of still does. The problem still MUST be resolved at the
authoritative nameservers.

Hope this helps --PSRC (software engineer, Google Public DNS)

Reply all
Reply to author
Forward
0 new messages