[ Fac Ut Vivas @ 26.09.2008. 16:47 ] @
Žao mi je što postavljam novu temu za ovo ali mi treba hitno.

Da li neko sa Telekomovog i neko sa Veratovog ADSL-a može da mi uradi nslookup i trace za mincex.cu i mx1.mincex.cu

Hvala svima na pomoći.
[ djricky @ 26.09.2008. 22:48 ] @
evo ti sa Verata:
root@v001:~# traceroute mincex.cu
traceroute to mincex.cu (200.55.135.10), 30 hops max, 40 byte packets
1 (192.168.1.1) 2.437 ms 2.413 ms 2.398 ms
2 airbus-380.vline.verat.net (85.222.161.17) 17.748 ms 19.596 ms 19.582 ms
3 airbus-380.vline.verat.net (85.222.161.17) 21.618 ms 23.048 ms 23.523 ms
4 213-163-36-21.pool.invitel.hu (213.163.36.21) 27.404 ms 30.837 ms 30.849 ms
5 213.163.53.221 (213.163.53.221) 31.635 ms 31.622 ms *
6 213-163-21-89.pool.invitel.hu (213.163.21.89) 38.509 ms 23.042 ms 23.010 ms
7 info-p0-ten2-2.vivendi-th.net (213.163.52.6) 24.400 ms 13.381 ms *
8 * ge-6-0-0.bud2core1.pantel.net (212.24.163.205) 15.858 ms 18.338 ms
9 POS4-0-1.ar2.VIE1.gblx.net (64.214.145.1) 23.355 ms 24.209 ms 24.190 ms
10 64.209.103.174 (64.209.103.174) 147.910 ms 150.631 ms 153.186 ms
11 newcom2.newcom-intl.com (204.14.40.2) 154.075 ms 154.035 ms 155.354 ms
12 mia-static-204-14-41-66.newcom-intl.com (204.14.41.66) 730.529 ms 719.670 ms 735.326 ms
13 200.0.16.102 (200.0.16.102) 718.059 ms 727.615 ms 726.936 ms
14 200.0.16.113 (200.0.16.113) 729.894 ms 718.939 ms 722.389 ms
15 200.0.16.141 (200.0.16.141) 726.384 ms 726.218 ms 727.622 ms
16 * * *
17 * * *
18 * * *
19 * * *
nemam Telekomov adsl, ali evo sa YUBC-ovog lg-a, koji koristi telekom:
traceroute to 200.55.135.14 (200.55.135.14), 30 hops max, 40 byte packets
1 YUBC-M10.telekom.yu (195.178.34.21) 0.939 ms 0.804 ms 0.740 ms
2 212.200.232.17 (212.200.232.17) 0.984 ms 1.009 ms 1.284 ms
MPLS Label=346128 CoS=0 TTL=1 S=1
3 212.200.227.234 (212.200.227.234) 0.988 ms 212.200.227.226 (212.200.227.226) 0.725 ms 212.200.227.234 (212.200.227.234) 0.871 ms
4 s4-0-0.ar1.VIE1.gblx.net (64.210.69.1) 13.718 ms 13.735 ms 13.854 ms
5 64.209.103.174 (64.209.103.174) 146.066 ms 146.851 ms 146.190 ms
6 newcom2.newcom-intl.com (204.14.40.2) 146.253 ms 146.197 ms 146.591 ms
7 mia-static-204-14-41-66.newcom-intl.com (204.14.41.66) 691.520 ms 699.527 ms 692.213 ms
8 200.0.16.82 (200.0.16.82) 671.580 ms 677.046 ms 672.311 ms
9 200.0.16.113 (200.0.16.113) 673.545 ms 673.086 ms 671.600 ms
10 200.0.16.141 (200.0.16.141) 674.034 ms 673.936 ms 671.092 ms
11 * * *
12 * * *

a evo sa OIX-a:
route-views.oregon-ix.net>traceroute mx1.mincex.cu
Translating "mx1.mincex.cu"...domain server (128.223.32.35) [OK]

Type escape sequence to abort.
Tracing the route to ns1.mincex.cu (200.55.135.14)

1 vl-51.uonet1-gw.uoregon.edu (128.223.51.2) [AS 3582] 4 msec 0 msec 0 msec
2 0.ge-0-1-0.uonet8-gw.uoregon.edu (128.223.3. [AS 3582] 0 msec 0 msec 4 msec
3 vl-205.ge-2-0-0.core0-gw.pdx.oregon-gigapop.net (198.32.165.217) 0 msec 0 msec 4 msec
4 vl-201.abilene-losa-gw.oregon-gigapop.net (198.32.165.194) 24 msec 28 msec 24 msec
5 64.57.28.39 [AS 11537] [MPLS: Label 100832 Exp 0] 52 msec 52 msec 52 msec
6 64.57.29.6 [AS 11537] 48 msec 52 msec 48 msec
7 so5-0-0-2488M.ar2.MIA1.gblx.net (67.17.106.37) [AS 3549] 136 msec 184 msec 132 msec
8 64.209.103.174 [AS 3549] 168 msec 312 msec 368 msec
9 newcom2.newcom-intl.com (204.14.40.2) [AS 32034] 120 msec 120 msec 120 msec
10 mia-static-204-14-41-66.newcom-intl.com (204.14.41.66) [AS 32034] 652 msec 648 msec 652 msec
11 200.0.16.82 [AS 11960] 648 msec 652 msec 648 msec
12 200.0.16.113 [AS 11960] 644 msec 652 msec 644 msec
13 200.0.16.141 [AS 11960] 668 msec 644 msec 640 msec
14 * * *
15 * * *
16 * * *
17 * * *


a gde je uopste ta mreza:
inetnum: 200.55.135.8/29
status: reallocated
owner: MCE
ownerid: CU-MCEM-LACNIC
responsible: Denis Carballo
address: Calle Infanta % 23 y Humbolt Vedado, 16,
address: 10100 - Ciudad de La Habana -
country: CU
phone: +53 7 55-0514 []
owner-c: DAR
tech-c: DAR
abuse-c: DAR
created: 20060413
changed: 20060413
inetnum-up: 200.55.128/19

nic-hdl: DAR
person: Daniel Ramos
e-mail: [email protected]
address: Ave Independencia y 19 de Mayo, 0,
address: 10600 - La Habana -
country: CU
phone: +53 7 337337 []
created: 20021011
changed: 20021209


Havana?? ("tamo je dobar koji ima, vremena i dima..." - Darko Rundek)

i sta je tacno problem? ja ga ne vidim?
[ Fac Ut Vivas @ 27.09.2008. 00:12 ] @
Pa problem je u tome što Telekomov DNS ne može da razreši mincex.cu "NS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out" za razliku od DNS servera drugih provajdera. A promena DNS-a na lokalnom računaru ne vredi jer je u pitanju slanje mejla sa telekomovog servera, koji valjda koristi telekomov DNS.
Svaki put se mail vrati sa porukom:

"Bad destination host 'DNS Soft Error looking
up mincex.cu (MX) while asking recursive_nameserver0.parent. Error was:
unable to reach nameserver on any valid IP' (delivery attempts: 0)"

Zvaću u ponedeljak tehničku podršku...

Nego kada si pitao šta je tačno problem, nije mi jasno... misliš da to što trace nije prošao do kraja ne predstavlja problem???

edit:
OK. Jel normalno da mogu da otvorim web stranicu www.mincex.cu a da ne mogu da uradim trace do te adrese? Nisu valjda sve pozatvarali sem porta 80?

[Ovu poruku je menjao Fac Ut Vivas dana 27.09.2008. u 01:33 GMT+1]
[ djricky @ 27.09.2008. 08:56 ] @
Citat:
Fac Ut Vivas: Jel normalno da mogu da otvorim web stranicu www.mincex.cu a da ne mogu da uradim trace do te adrese? Nisu valjda sve pozatvarali sem porta 80?

Da. probaj npr. da uradis trace do EUnetovog sajta ili Sezampro ili telekom.yu?
[ djricky @ 27.09.2008. 12:16 ] @
Searching for mincex.cu. MX record at D.ROOT-SERVERS.NET. [128.8.10.90] ...took 96 ms
Searching for mincex.cu. MX record at RIP.PSG.COM. [147.28.0.39] ...took 186 ms
Searching for mincex.cu. MX record at ns2.mincex.cu. [200.55.135.12] ...took 641 ms

MX record found: 20 mx2.mincex.cu.
MX record found: 10 mx1.mincex.cu.
Domain Type TTL Answer
mincex.cu. NS 604800 ns1.mincex.cu.
mincex.cu. NS 604800 ns2.mincex.cu.
mincex.cu. MX 604800 20 mx2.mincex.cu.
mincex.cu. MX 604800 10 mx1.mincex.cu.


Total elapsed query time: 923 ms


kako vidim, oba NS-a su na istom subnetu, cak je i MX na istoj masini gde i jedan NS takodje, TTL je ogroman, a ocigledno je da je veza do Kube realizovana preko satelistkog linka... (hint: ping preko 700ms)