[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Why can't I reach master ?



John, the route is breaking down in the middle so it looks like
different routing rules are being triggered on hosts out of your control
(which implies that it's not your routing setup).  Are you *sure* that
you're sending to the same address?  Check the IP you're using on both
machines for master: DNS, /etc/hosts, NIS, ..., whatever nsswitch.conf is
calling out on hosts line; if you're using DNS, check that resolv.conf
is pointing to trusted servers or that zone file sources are correct if
you're running a private named.

I get 209.41.108.5 doing a "ypmatch master.debian.org hosts.byname" which
refers to a private (caching) server which refers to *.root-servers.net.
for external lookups.

Using nslookup, I get the following name servers for debian.org (from
{a|b}.root-servers.net):

> debian.org.
Server:  b.root-servers.net
Address:  128.9.0.107

Name:    debian.org
Served by:
- SAMOSA.debian.org
          209.249.97.234
          debian.org
- SAENS.debian.org
          207.69.194.216
          debian.org
- NS1.LDSOL.COM
          62.161.210.241
          debian.org
- NS2.CISTRON.NL

          debian.org
- OPEN.HANDS.COM
          195.224.53.39
          debian.org

# Note: ns2.cistron.nl doesn't have an address known to this root-server,
# how odd?  a.root-servers.net knows it.

> lserver a.root-servers.net
Default Server:  a.root-servers.net
Address:  198.41.0.4

> debian.org.
Server:  a.root-servers.net
Address:  198.41.0.4

Name:    debian.org
Served by:
- SAMOSA.debian.org
          209.249.97.234
          debian.org
- SAENS.debian.org
          207.69.194.216
          debian.org
- NS1.LDSOL.COM
          62.161.210.241
          debian.org
- NS2.CISTRON.NL
          195.64.68.28
          debian.org
- OPEN.HANDS.COM
          195.224.53.39
          debian.org

###
Ok, all the others, except ns2.cistron.nl seems to have consistent IP's
known across multiple root-servers (had to check because I was having
problems with getting *any* response for debian.org domain as you'll see).

Ok, doing lookups on samosa - no response:
> server samosa.debian.org
Default Server:  samosa.debian.org
Address:  209.249.97.234

> master
Server:  samosa.debian.org
Address:  209.249.97.234

*** samosa.debian.org can't find master: No response from server
> www
Server:  samosa.debian.org
Address:  209.249.97.234

*** samosa.debian.org can't find www: No response from server
> master.debian.org
Server:  samosa.debian.org
Address:  209.249.97.234


> master.debian.org.
Server:  samosa.debian.org
Address:  209.249.97.234

*** samosa.debian.org can't find master.debian.org.: No response from server
> 

## (Missing responses were ^C'd)

Ok, trying saens:
Same thing - not good.  Where did my lookup come from?  Trying other
debian name servers.  Ok, got an answer from open.hands.com.  (samosa and
saens may be up but may have my queries blocked - i.e., this may be a
security issue rather than an availability issue - maybe).

Ok, results from open.hands.com:

> server open.hands.com
Default Server:  open.hands.com
Address:  195.224.53.39

> set domain=debian.org.
> master
Server:  open.hands.com
Address:  195.224.53.39

Name:    master.debian.org
Address:  209.41.108.5

> 


However, I was just trying to confirm the IP above comes from a trusted
source, but you should probably do that yourself anyway (unless you
trust me :-)).

Ok, that done, you need to make sure that when your machine resolves
master, it gets this address, or upload to an IP address if your upload
programs/scripts can do that.



On Tue, Jul 13, 1999 at 01:09:46AM -0700, John Lapeyre wrote:
>   Do any of you "computer geniuses" know why I can reach master
> from some machines and not from others ?  I can't reach it from
> a machine running potato.  I can reach it from one running Digital
> unix.  Does this make any sense ?
> 
>   Here is traceroute on a machine that can't reach it,
> traceroute to master.debian.org (209.176.56.5), 30 hops max, 40 byte packets
>  1  128.196.30.1 (128.196.30.1)  0.971 ms  0.925 ms  0.94 ms
>  2  Pancho.Telcom.Arizona.EDU (128.196.1.10)  5.66 ms  4.353 ms  4.559 ms
>  3  Mongo-POS0-3-Pancho.telcom.Arizona.EDU (192.80.43.5)  0.895 ms  0.856 ms  0.927 ms
>  4  Wyatt-POS5-0-0-Mongo.telcom.Arizona.EDU (192.80.43.10)  1.272 ms  1.221 ms  1.011 ms
>  5  205.171.55.149 (205.171.55.149)  18.77 ms  18.834 ms  18.827 ms
>  6  den-core-02.inet.qwest.net (205.171.16.137)  18.834 ms  18.823 ms  19.194 ms
>  7  kcm-core-01.inet.qwest.net (205.171.5.49)  29.333 ms  29.224 ms  29.732 ms
>  8  chi-core-03.inet.qwest.net (205.171.5.209)  41.928 ms  41.881 ms  41.84 ms
>  9  chi-core-02.inet.qwest.net (205.171.20.29)  41.897 ms  42.31 ms  42.383 ms
>  10  wdc-core-01.inet.qwest.net (205.171.5.225)  67.905 ms  67.893 ms  68.086 ms
>  11  wdc-brdr-01.inet.qwest.net (205.171.24.30)  68.306 ms  68.125 ms  68.036 ms
>  12  205.171.4.242 (205.171.4.242)  69.351 ms  69.189 ms  69.83 ms
>  13  sl-bb10-rly-0-2.sprintlink.net (144.232.0.37)  83.476 ms  70.34 ms  69.736 ms
>  14  sl-bb10-orl-1-0.sprintlink.net (144.232.9.62)  85.751 ms  86.104 ms  85.346 ms
>  15  sl-bb10-fw-4-1.sprintlink.net (144.232.9.105)  111.762 ms  111.64 ms  111.693 ms
>  16  sl-bb13-fw-9-0.sprintlink.net (144.232.11.170)  112.417 ms  112.17 ms  112.473 ms
>  17  sl-gw13-fw-0-0-0.sprintlink.net (144.232.11.62)  113.148 ms  112.377 ms  112.702 ms
>  18  sl-dnetfw-1-0-T3.sprintlink.net (144.228.137.6)  114.187 ms  114.149 ms  113.826 ms
>  19  * *                     
> 
> Here is a machine that can reach it:
> traceroute to master.debian.org (209.41.108.5), 30 hops max, 40 byte packets
>  1  128.196.30.1 (128.196.30.1)  1 ms  1 ms  1 ms
>  2  Pancho.Telcom.Arizona.EDU (128.196.1.10)  7 ms  7 ms  5 ms
>  3  Mongo-POS0-3-Pancho.telcom.Arizona.EDU (192.80.43.5)  1 ms  1 ms  1 ms
>  4  Wyatt-POS5-0-0-Mongo.telcom.Arizona.EDU (192.80.43.10)  1 ms  1 ms  1 ms
>  5  205.171.55.149 (205.171.55.149)  19 ms  19 ms  19 ms
>  6  den-core-01.inet.qwest.net (205.171.16.109)  20 ms  19 ms  19 ms
>  7  sfo-core-03.inet.qwest.net (205.171.5.35)  43 ms  44 ms  42 ms
>  8  sfo-core-02.inet.qwest.net (205.171.18.9)  43 ms  42 ms  43 ms
>  9  205.171.5.129 (205.171.5.129)  43 ms  44 ms  43 ms
> 10  sjo-edge-05.inet.qwest.net (205.171.22.46)  44 ms  44 ms  43 ms
> 11  205.171.4.10 (205.171.4.10)  45 ms  45 ms  44 ms
> 12  sl-bb12-sj-9-0.sprintlink.net (144.232.3.86)  44 ms  43 ms  44 ms
> 13  sl-bb11-stk-10-0.sprintlink.net (144.232.9.170)  45 ms  46 ms  46 ms
> 14  sl-bb10-stk-9-0.sprintlink.net (144.232.4.105)  46 ms  45 ms  46 ms
> 15  sl-bb10-ana-8-0.sprintlink.net (144.232.8.90)  56 ms  57 ms  56 ms
> 16  sl-bb10-fw-6-0.sprintlink.net (144.232.8.173)  96 ms  96 ms  96 ms
> 17  144.232.11.9 (144.232.11.9)  97 ms  97 ms  96 ms
> 18  sl-gw13-fw-8-0-0.sprintlink.net (144.232.11.66)  96 ms  97 ms  97 ms
> 19  sl-dnetfw-1-0-T3.sprintlink.net (144.228.137.6)  98 ms  98 ms  99 ms
> 20  unicomp-3.DllsTX.savvis.net (209.176.32.58)  100 ms  100 ms  100 ms
> 21  master.debian.org (209.41.108.5)  100 ms  100 ms  100 ms
>                                                                                
> 
> 
> -- 
> John Lapeyre <lapeyre@physics.arizona.edu>,  lapeyre@debian.org
> Tucson,AZ     http://www.physics.arizona.edu/~lapeyre
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 

-- 
Steve Bowman <sbowman@goodnet.com><bowmanc@acm.org>
Buckeye, AZ

Powered by Debian GNU/Linux <http://www.debian.org>


Reply to: