Continuing problem with "portsnap"

[Vincent Hoffman]

On 02/11/2010 14:33, Jerry wrote:
> On Tue, 02 Nov 2010 13:48:12 +0000
> Vincent Hoffman <vince at unsane.co.uk> articulated:
>
>>
>> Sounds like DNS to me.
>> what output do you get from
>> dig +trace portsnap.freebsd.org
> $ dig +trace portsnap.freebsd.org
>
> ; <<>> DiG 9.6.2-P2 <<>> +trace portsnap.freebsd.org
> ;; global options: +cmd
> .			18158	IN	NS	h.root-servers.net.
> .			18158	IN	NS	a.root-servers.net.
> .			18158	IN	NS	d.root-servers.net.
> .			18158	IN	NS	k.root-servers.net.
> .			18158	IN	NS	g.root-servers.net.
> .			18158	IN	NS	i.root-servers.net.
> .			18158	IN	NS	f.root-servers.net.
> .			18158	IN	NS	e.root-servers.net.
> .			18158	IN	NS	j.root-servers.net.
> .			18158	IN	NS	b.root-servers.net.
> .			18158	IN	NS	c.root-servers.net.
> .			18158	IN	NS	l.root-servers.net.
> .			18158	IN	NS	m.root-servers.net.
> ;; Received 228 bytes from 209.18.47.62#53(209.18.47.62) in 10 ms
>
> ;; connection timed out; no servers could be reached
>
Hmm you should be seeing something like
jhary at ostracod
(13:48:49 <~>) 0 $ dig +trace portsnap.freebsd.org

; <<>> DiG 9.6.2-P2 <<>> +trace portsnap.freebsd.org
;; global options: +cmd
.            424412    IN    NS    c.root-servers.net.
.            424412    IN    NS    l.root-servers.net.
.            424412    IN    NS    f.root-servers.net.
.            424412    IN    NS    g.root-servers.net.
.            424412    IN    NS    k.root-servers.net.
.            424412    IN    NS    h.root-servers.net.
.            424412    IN    NS    b.root-servers.net.
.            424412    IN    NS    i.root-servers.net.
.            424412    IN    NS    j.root-servers.net.
.            424412    IN    NS    d.root-servers.net.
.            424412    IN    NS    a.root-servers.net.
.            424412    IN    NS    m.root-servers.net.
.            424412    IN    NS    e.root-servers.net.
;; Received 332 bytes from 127.0.0.1#53(127.0.0.1) in 1 ms

org.            172800    IN    NS    d0.org.afilias-nst.org.
org.            172800    IN    NS    c0.org.afilias-nst.info.
org.            172800    IN    NS    b0.org.afilias-nst.org.
org.            172800    IN    NS    a2.org.afilias-nst.info.
org.            172800    IN    NS    b2.org.afilias-nst.org.
org.            172800    IN    NS    a0.org.afilias-nst.info.
;; Received 440 bytes from 128.8.10.90#53(d.root-servers.net) in 125 ms

freebsd.org.        86400    IN    NS    ns3.isc-sns.info.
freebsd.org.        86400    IN    NS    ns2.isc-sns.com.
freebsd.org.        86400    IN    NS    ns1.isc-sns.net.
;; Received 126 bytes from 2001:500:b::1#53(c0.org.afilias-nst.info) in
69 ms

portsnap.freebsd.org.    3600    IN    A    204.109.56.116
freebsd.org.        3600    IN    NS    ns1.isc-sns.net.
freebsd.org.        3600    IN    NS    ns3.isc-sns.info.
freebsd.org.        3600    IN    NS    ns2.isc-sns.com.
;; Received 246 bytes from 2001:5a0:10::1#53(ns3.isc-sns.info) in 47 ms


It should recurse through the DNS hierarchy, starting at the servers for
.  then the servers for org then the servers for freebsd and finally
give you a result.

I guess this means either you or your ISP is filtering access on port 53
other than to their severs, or else your ISP has a connectivity issue.
can you currently resolve any .org domains? (netbsd.org or openbsd.org
or apache.org spring to mind)


Vince