Da li je u pitanju neki problem sa DNS-om ???

Pozdrav.
Vec duze vrijeme bezuspjesno pokusavamo da rijesimo problem, koji se, cini mi se, odnosi na DNS.

Preko UTP-a sam povezan na swich koji je opet povezan na racunar preko kojeg dobijam izlaz na internet (ukupna razdaljina manja od 100m).

Stranice se JAKO SPORO ucitavaju (dial-up je mnogo brzi sto se toga tice), ali je download fajlova sa interneta sasvim OK - (20 do 40 KB/s - kilobajta)!
Posto racunar, preko kojeg ja imam izlaz na internet, ima link od 2Mb/s - megabita, sumnjam na to da DNS nije najbolje podesen i da resolving ne radi kako treba, pa Vam se obracam u nadi da cete imati neki prijedlog sta da se radi?
Steta da ovako dobra konekcija bude neupotrebljiva za surf.

Ovo su podesavanja LAN konekcije mog racunara:

IP: 10.1.1.49
Subnet mask: 255.0.0.0
Default gateway: 10.10.1.1
Preffered DNS : 10.10.1.1
Alternate DNS: 195.10.1.1

Nesto mi je sumnjivo ovo vezano za Default gateway i Preffered DNS - imaju istu adresu?! Kako se barem meni cini, u polje Default gateway trebalo bi upisat IP adresu racunara koji je vec povezan na net! To je samo moje skromno misljenje. Ne znam - nisam siguran...


Uradio sam ping -n 100 i za Alternate DNS i za gateway odn. Preffered DNS kako bih vam bolje predocio problem i evo rezultata:

C:\Documents and Settings\bajke>ping 195.222.32.10 -n 100

Pinging 195.222.32.10 with 32 bytes of data:

Request timed out.
Reply from 195.222.32.10: bytes=32 time=28ms TTL=246
Request timed out.
Request timed out.
Reply from 195.222.32.10: bytes=32 time=21ms TTL=246
Reply from 195.222.32.10: bytes=32 time=21ms TTL=246
Request timed out.
Reply from 195.222.32.10: bytes=32 time=22ms TTL=246
Reply from 195.222.32.10: bytes=32 time=28ms TTL=246
Request timed out.
Reply from 195.222.32.10: bytes=32 time=22ms TTL=246
Reply from 195.222.32.10: bytes=32 time=21ms TTL=246
Reply from 195.222.32.10: bytes=32 time=22ms TTL=246
Reply from 195.222.32.10: bytes=32 time=32ms TTL=246
Reply from 195.222.32.10: bytes=32 time=31ms TTL=246
Request timed out.
Request timed out.
Reply from 195.222.32.10: bytes=32 time=23ms TTL=246
Reply from 195.222.32.10: bytes=32 time=21ms TTL=246
Request timed out.
Reply from 195.222.32.10: bytes=32 time=44ms TTL=246
Reply from 195.222.32.10: bytes=32 time=23ms TTL=246
Request timed out.
Reply from 195.222.32.10: bytes=32 time=26ms TTL=246
Request timed out.
Reply from 195.222.32.10: bytes=32 time=21ms TTL=246
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 195.222.32.10: bytes=32 time=21ms TTL=246
Request timed out.
Reply from 195.222.32.10: bytes=32 time=22ms TTL=246
Request timed out.
Reply from 195.222.32.10: bytes=32 time=40ms TTL=246
Request timed out.
Request timed out.
Reply from 195.222.32.10: bytes=32 time=23ms TTL=246
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 195.222.32.10: bytes=32 time=112ms TTL=246
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 195.222.32.10: bytes=32 time=73ms TTL=246
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 195.222.32.10:
Packets: Sent = 100, Received = 22, Lost = 78 (78% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 112ms, Average = 31ms

Kao sto se vidi mnogo puta se pojavilo timed out cak 73% izgubljenih
paketa! Ovi rezultati su nekad i mnogo gori!


Kada pingujem Default gateway odnosno Preffered DNS stvari su mnogo bolje:

C:\Documents and Settings\bajke>ping 10.10.1.1 -n 100

Pinging 10.10.1.1 with 32 bytes of data:

Reply from 10.10.1.1: bytes=32 time=3ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=3ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=5ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=3ms TTL=128
Reply from 10.10.1.1: bytes=32 time=7ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=3ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=4ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=4ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=2ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128
Reply from 10.10.1.1: bytes=32 time=1ms TTL=128

Ping statistics for 10.10.1.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 7ms, Average = 1ms

Sta da se radi po ovom pitanju?

Ja ne vidim da ti se adresa 195.222.32.10 pojavljuje kao dns server igde.

Da li je do dns-a ili nije je najlakse proveriti. Ubaci adrese dns-a tvog provajdera kao Preffered DNS i vrlo brzo ces uociti.
Probaj npr sa ovima:
Teol.net dns1 - 81.93.64.1
Teol.net dns2 - 81.93.64.9

ns1.bih.net.ba - (upravo onaj ip) 195.222.32.10
ns2.bih.net.ba - 195.222.32.20

Sa druge strane, ping loss od 78% je prilicno katastrofalan. Ja bih prvo pokusao da saznam zbog cega je takav. Moze biti od loseg linka pa do nekog ko recimo p2p saobracajem ubija ceo protok. Koliko vas deli taj link? Koja vrsta linka je u pitanju?

---

probaj alternate dns prominit

IP: 10.1.1.49
Subnet mask: 255.0.0.0
Default gateway: 10.10.1.1
Preffered DNS : 10.10.1.1
// Alternate DNS: 195.10.1.1

Alternate DNS: 10.10.1.2

---

Da li to vazi za bilo koju Web stranicu sa svakog racunara? Probaj otvarati stranice po IP adresi. U tom slucaju zaobilazis DNS, tj. nije ti potreban. Ako je situacija ista, problem je svakako negde drugde, a ne u DNS-u.

Posto je link 2Mbps, pretpostavljam da je mreza veca. Koliko je racunara na mrezi? Kakav je taj racunar ka Net-u, tj. koji OS i koji servisi se vrte na njemu? Imate li svoj DNS, tj. imate li domen ili radnu grupu? Kakav je File Sharing u LAN-u? Eto nekoliko pitanja, cisto da napomenem da je i poznavanje strukture mreze potrebno da bi resili taj problem.

Pozdrav

Tako je, kao Preffered DNS ti je naveden računar preko kojeg izlaziš na net što je u redu ako je na njemu instaliran DNS Server. Ako nije onda bi taj preffered morao da ti bude DNS server koji ti daje provajder. To što si pingovao svoj default gateway ti ne govori ništa, tj. u lokalnoj ste mreži pa se podrazumeva da imaš brzu vezu s njim, ali to ne mora imati nikakve veze sa DNS-om ako on nije istovremeno i DNS server.

Kad malo bolje razmislim, tvoja situacija nema nikakve veze sa DNS-om. Zasto? Pa kada si pingovao 195.222.32.10 (ma sta da je), ti si pingovao po IP adresi, a tu DNS nema nikakvu funkciju, pa izostanak Reply-a zavisi od neceg drugog.
Cak i kada pingujes po imenu, imas kraci ili duzi Time-Out dok neki DNS ne odredi IP adresu, a posle toga je on zavrsio svoj posao i za samo pingovanje vise nije odgovoran.
Problem treba traziti u tom racunaru preko koga izlazite na Net ili kod provajdera.

Da, ali ako mu je taj 195.* stvarno DNS server, onda bi to moglo da ukaže na probleme u vezi sa DNS serverom i samim tim sporo razrešavanje adresa, ili grešim?

Da, to bi ukazivalo na "los put" do tog DNS-a, a razresavanje mozda radi odlicno. Rezultat je, naravno, sporo razresavanje.
Moj ping do tog 195.222.32.10 je 100% i iznosi 49ms, a do njegovog drugog DNS-a (195.10.1.1) takodje 100% ali 1500ms.

Trebalo bi vise da nam kaze o svojoj mrezi i kako je izveden izlazak na Net.

@PBajic

Koje su to adrese 195.222.32.10 i 195.10.1.1? Sta se desava kada pingujes Google?
Kao sto nagovestava Optix ima li mogucnosti da ti budes jedini korisnik Net-a, npr. posle radnog vremena.

Evo kako izgleda pingovanje tog DNSa sa 1 mbps optickog linka.


Pinging 195.222.32.10 with 32 bytes of data:

Reply from 195.222.32.10: bytes=32 time=14ms TTL=249
Reply from 195.222.32.10: bytes=32 time=15ms TTL=249
Reply from 195.222.32.10: bytes=32 time=11ms TTL=249
Reply from 195.222.32.10: bytes=32 time=9ms TTL=249

Ping statistics for 195.222.32.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 15ms, Average = 12ms

To sto kod tebe lose radi znaci da imas neki problem sa linkom do neta, ali sa druge strane, ak dobro radi download ... hmm. Probaj da promenish default DNS:


Molim te, probaj da pingujesh nesto drugo (npr www.yahoo.com) pa posalji rezultate.

Hvala vam na brzim odgovorima.
Problem je dakle ipak bio u linku sa ISP-om.
Adrese ovih DNS-a su uzete u obzir, sto je dalo neke dobre rezultate...(ping bolji i konstantniji oko 30-40 ms)

Mreza je klon BG Wireless-a. Kaci se wireless-om na ISP-a. Problem je bio u linku izmedju Gateway-a i ISP-a. Problem resen izmestanjem antene.

U mrezi rade FTP i DC servisi ali nisu bitni u ovom slucaju. Gateway je win 2000 pro.
ETO...