Constantin Gavrilescu wrote:
Cam pe la 11/29/2005 10:13 AM, Tarhon-Onu Victor scrise:
Pune-ti la punct local un caching nameserver si seteaza-l pe ala
ca ns pe statiile tale. La acel caching nameserver poti sa pui la
forwarders o lista de ns-uri, macar daca pica unul vei astepta sa
rezolve doar hosturile care nu sint deja in cache.
Caching nu face si resolverul normal C?
AFAIK, nu
n-ai decit sa pui un DNS pe o alta masina decit cea de test, sa stai cu tcpdump
pe interfata externa, sa dai de zor host www.xxx.com si sa urmaresti cum la
fiecare comanda mai apare cite o cerere. ete, ca sa te scutesc de timpul pt test:
consola 1:tcpdump port 53 -n
06:21:29.475204 IP 192.168.1.2.1037 > 192.168.100.101.domain: 40601+ A?
www.xxx.com. (29)
06:21:29.487699 IP 192.168.100.101.domain > 192.168.1.2.1037: 40601 1/2/2 A
206.207.85.33 (123)
06:21:29.490653 IP 192.168.1.2.1038 > 192.168.100.101.domain: 43306+ AAAA?
www.xxx.com. (29)
06:21:29.503298 IP 192.168.100.101.domain > 192.168.1.2.1038: 43306 0/1/0 (90)
06:21:29.529199 IP 192.168.1.2.1039 > 192.168.100.101.domain: 60557+ MX?
www.xxx.com. (29)
06:21:29.540352 IP 192.168.100.101.domain > 192.168.1.2.1039: 60557 0/1/0 (90)
06:21:32.742096 IP 192.168.1.2.1039 > 192.168.100.101.domain: 41310+ A?
www.xxx.com. (29)
06:21:32.751973 IP 192.168.100.101.domain > 192.168.1.2.1039: 41310 1/2/2 A
206.207.85.33 (123)
06:21:32.755276 IP 192.168.1.2.1040 > 192.168.100.101.domain: 44850+ AAAA?
www.xxx.com. (29)
06:21:32.766969 IP 192.168.100.101.domain > 192.168.1.2.1040: 44850 0/1/0 (90)
06:21:32.793616 IP 192.168.1.2.1041 > 192.168.100.101.domain: 18156+ MX?
www.xxx.com. (29)
06:21:32.804333 IP 192.168.100.101.domain > 192.168.1.2.1041: 18156 0/1/0 (90)
06:21:39.326359 IP 192.168.1.2.1041 > 192.168.100.101.domain: 19244+ A?
www.xxx.com. (29)
06:21:39.339279 IP 192.168.100.101.domain > 192.168.1.2.1041: 19244 1/2/2 A
206.207.85.33 (123)
06:21:39.341980 IP 192.168.1.2.1042 > 192.168.100.101.domain: 32873+ AAAA?
www.xxx.com. (29)
06:21:39.352444 IP 192.168.100.101.domain > 192.168.1.2.1042: 32873 0/1/0 (90)
06:21:39.378367 IP 192.168.1.2.1043 > 192.168.100.101.domain: 44057+ MX?
www.xxx.com. (29)
06:21:39.392695 IP 192.168.100.101.domain > 192.168.1.2.1043: 44057 0/1/0 (90)
simultan, in consola2:
[EMAIL PROTECTED] ~]$ host www.xxx.com
www.xxx.com has address 206.207.85.33
[EMAIL PROTECTED] ~]$ host www.xxx.com
www.xxx.com has address 206.207.85.33
[EMAIL PROTECTED] ~]$ host www.xxx.com
www.xxx.com has address 206.207.85.33
Bind face si load balancing round robin, din cate am vazut eu cu tcpdump.
bind face multe, daca il rogi frumos. pt problema initiala a threadului, orice
caching nameserver e suficient. ca e facut cu bind, cu minunea lui dan, cu
MaraDNS, cu rahatul lui M$ sau cu un negrisor mic care se uita repede in
cartile de telefon, e nesemnificativ
--
Daca ai vointa, poti sa muti si muntii din loc. Daca ai creier, ii lasi acolo,
ca nu te deranjeaza.
_______________________________________________
RLUG mailing list
[email protected]
http://lists.lug.ro/mailman/listinfo/rlug
