Jump to content

SUBIECTE NOI
« 1 / 5 »
RSS
De unde cumparați legume si fructe?

Samsung S21 ultra

Site-uri matrimoniale serioase

Plasa de umbrire peste gard de pl...
 O smecherie pe care nu o inteleg

Balcon parter fara acte

unde gasesc un speed bag in bucur...

Programe TV cu altfel de sporturi
 Laptop "bun la toate" max...

navigatie noua vw tiguan

ctfmon.exe - System Error (in Saf...

Ați prins vremurile cand 120 Volț...
 Whatsapp nu afișeaza numele ...

Medii admitere Politehnica Bucure...

Se extinde Baza de la Kogalniceanu

Politist mutilat de caine in curt...
 

Probleme server DNS (bind9)

- - - - -
  • Please log in to reply
7 replies to this topic

#1
caracal

caracal

    Junior Member

  • Grup: Members
  • Posts: 226
  • Înscris: 30.01.2007
Salut, am un server pe care rulez bind9 ca server DNS. Totul a functionat perfect, de ani buni, pana azi dimineata. Cand dau ping din extern catre orice hostname tinut pe server, imi da "unknown host". De pe server functioneaza. Dig functioneaza de pe localhost, dar de pe orice alt server, nu (inclusiv de pe serverul slave).

master:
root@rullz:/var/log# dig rullz.us
; <<>> DiG 9.9.5-9+deb8u6-Debian <<>> rullz.us
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56719
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;rullz.us.					 IN	 A
;; ANSWER SECTION:
rullz.us.			 3600 IN	 A	 86.126.136.56
;; AUTHORITY SECTION:
rullz.us.			 3600 IN	 NS	 ns2.rullz.us.
rullz.us.			 3600 IN	 NS	 ns.rullz.us.
;; ADDITIONAL SECTION:
ns.rullz.us.		 3600 IN	 A	 86.126.136.56
ns2.rullz.us.		 3600 IN	 A	 195.238.90.1
;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jun 29 12:12:34 EEST 2016
;; MSG SIZE rcvd: 120
root@rullz:/var/log#


slave:
{root@serverblue:}[~]: dig rullz.us
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-25.P1.el5_11.3 <<>> rullz.us
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20486
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;rullz.us.					 IN	 A
;; Query time: 0 msec
;; SERVER: 195.238.90.1#53(195.238.90.1)
;; WHEN: Wed Jun 29 12:13:15 2016
;; MSG SIZE rcvd: 26
{root@serverblue:}[~]:

Bind ruleaza:
root@rullz:/var/log# netstat -an | grep ^udp | grep 53
udp	 0	 0 86.126.136.56:53	 0.0.0.0:*
udp	 0	 0 127.0.0.1:53		 0.0.0.0:*
udp6	 0	 0 :::5353				 :::*
root@rullz:/var/log#

tcpdump nu captureaza nimic:
root@rullz:/var/log# tcpdump -n -nn -tttt -i ppp0 port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel

Portul nu este blocat in firewall (nici nu s-a umblat la firewall).

Edited by caracal, 29 June 2016 - 11:18.


#2
Mihai_3

Mihai_3

    我會回來的...

  • Grup: Senior Members
  • Posts: 10,039
  • Înscris: 26.04.2007
ciudat .... la mine pare sa fie OK..
..Attached File  www.jpg   277.71K   13 downloads

desemnea vad ca ai 53 open ....
ceea ce este OK.

Edited by Mihai_3, 29 June 2016 - 12:27.


#3
caracal

caracal

    Junior Member

  • Grup: Members
  • Posts: 226
  • Înscris: 30.01.2007
Ceea ce e ciudat e ca la tine functioneaza :) Am incercat si http://dnscheck.pingdom.com/ si http://mxtoolbox.com/ si http://www.intodns.com/. Cannot find hostname. Nu mai inteleg nimic.

#4
Mihai_3

Mihai_3

    我會回來的...

  • Grup: Senior Members
  • Posts: 10,039
  • Înscris: 26.04.2007
atientie insa ca eu am directionat catre serverul tau cererile ,,,,,
insa nu este propagat in internet.

https://www.whatsmydns.net/#A/rullz.us

vezi poate nu ai platit domeniul Posted Image

Edited by Mihai_3, 29 June 2016 - 12:44.


#5
caracal

caracal

    Junior Member

  • Grup: Members
  • Posts: 226
  • Înscris: 30.01.2007
Pai serverul meu (rullz.us) rezolva tot. Problema este ca orice altceva nu rezolva hostname-urile configurate in bind-ul de pe serverul meu. Nici macar serverul slave (195.238.90.1) nu le rezolva.

#6
Mihai_3

Mihai_3

    我會回來的...

  • Grup: Senior Members
  • Posts: 10,039
  • Înscris: 26.04.2007
nu vreau sa vorbesc cu pacat insa s-ar putea sa fie blocat din cauza continutului...
vorbesc de livejasmin, bani de acasa ...stii tu la ce ma refer.

Poate o sa te intrebi cine anume ?!?!
my best guess: chiar .us domain master.
sa mai asteptam si alte pareri ...

Edited by Mihai_3, 29 June 2016 - 13:00.


#7
caracal

caracal

    Junior Member

  • Grup: Members
  • Posts: 226
  • Înscris: 30.01.2007
.us nu cred. Continutul este din 2011 si nu este pe .us oricum.
In fine, nu cred ca are legatura cu asta. Ma gandesc ca au blocat cei de la RDS portul 53. Altceva nu vad, pentru ca a mers atata timp si nu s-a intervenit de foarte mult timp asupra setarilor bind.

L.E.: a aparut trafic si pe tcpdump:
root@rullz:/var/log# tcpdump -n -nn -tttt -i ppp0 port 53
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ppp0, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes


2016-06-29 14:09:01.329229 IP 86.126.136.56.42836 > 200.10.60.53.53: 21376% [1au] PTR? 153.192.133.181.in-addr.arpa. (57)
2016-06-29 14:09:01.561619 IP 200.10.60.53.53 > 86.126.136.56.42836: 21376- 0/11/1 (529)
2016-06-29 14:09:01.563335 IP 86.126.136.56.12192 > 200.229.248.10.53: 27724% [1au] A? a.arpa.dns.br. (42)
2016-06-29 14:09:01.563708 IP 86.126.136.56.63252 > 192.43.172.30.53: 20207% [1au] A? ns3.afrinic.net. (44)
2016-06-29 14:09:01.563864 IP 86.126.136.56.19968 > 200.229.248.10.53: 31300% [1au] AAAA? a.arpa.dns.br. (42)
2016-06-29 14:09:01.563959 IP 86.126.136.56.60497 > 162.159.25.153.53: 17923% [1au] A? lacnic.authdns.ripe.net. (52)
2016-06-29 14:09:01.564030 IP 86.126.136.56.52228 > 162.159.25.153.53: 138% [1au] AAAA? lacnic.authdns.ripe.net. (52)
2016-06-29 14:09:01.564534 IP 86.126.136.56.11313 > 200.3.13.11.53: 44928% [1au] PTR? 153.192.133.181.in-addr.arpa. (57)
2016-06-29 14:09:01.564761 IP 86.126.136.56.31708 > 192.43.172.30.53: 287% [1au] AAAA? ns3.afrinic.net. (44)
2016-06-29 14:09:01.567015 IP 86.126.136.56.35804 > 192.36.148.17.53: 65353% [1au] NS? . (28)
2016-06-29 14:09:01.567263 IP 86.126.136.56.12688 > 192.36.148.17.53: 16067% [1au] A? ns-lacnic.nic.mx. (45)
2016-06-29 14:09:01.567416 IP 86.126.136.56.31647 > 192.36.148.17.53: 26364% [1au] AAAA? ns-lacnic.nic.mx. (45)
2016-06-29 14:09:01.569775 IP 192.36.148.17.53 > 86.126.136.56.12688: 16067- 0/8/9 (506)
2016-06-29 14:09:01.569927 IP 192.36.148.17.53 > 86.126.136.56.35804: 65353*- 14/0/25 NS j.root-servers.net., NS c.root-servers.net., NS g.root-servers.net., NS l.root-servers.net., NS a.root-servers.net., NS i.root-servers.net., NS e.root-servers.net., NS m.root-servers.net., NS d.root-servers.net., NS b.root-servers.net., NS f.root-servers.net., NS k.root-servers.net., NS h.root-servers.net., RRSIG (913)
2016-06-29 14:09:01.570727 IP 192.36.148.17.53 > 86.126.136.56.31647: 26364- 0/8/9 (506)
2016-06-29 14:09:01.572342 IP 86.126.136.56.62419 > 200.94.176.1.53: 34785% [1au] A? ns-lacnic.nic.mx. (45)
2016-06-29 14:09:01.573392 IP 86.126.136.56.42727 > 200.94.176.1.53: 29794% [1au] AAAA? ns-lacnic.nic.mx. (45)
2016-06-29 14:09:01.596511 IP 162.159.25.153.53 > 86.126.136.56.60497: 17923*- 2/6/1 A 193.0.9.11, RRSIG (369)
2016-06-29 14:09:01.597185 IP 162.159.25.153.53 > 86.126.136.56.52228: 138*- 2/6/1 AAAA 2001:67c:e0::11, RRSIG (381)
2016-06-29 14:09:01.601788 IP 200.229.248.10.53 > 86.126.136.56.19968: 31300*- 0/4/1 (502)
2016-06-29 14:09:01.602798 IP 200.229.248.10.53 > 86.126.136.56.12192: 27724*- 2/7/9 A 200.160.11.50, RRSIG (1310)
2016-06-29 14:09:01.612742 IP 192.43.172.30.53 > 86.126.136.56.63252: 20207- 0/9/15 (729)
2016-06-29 14:09:01.613306 IP 86.126.136.56.53650 > 196.216.2.1.53: 13259% [1au] A? ns3.afrinic.net. (44)
2016-06-29 14:09:01.614999 IP 192.43.172.30.53 > 86.126.136.56.31708: 287- 0/9/15 (729)
2016-06-29 14:09:01.615411 IP 86.126.136.56.23890 > 196.216.2.1.53: 32777% [1au] AAAA? ns3.afrinic.net. (44)
2016-06-29 14:09:01.755649 IP 200.94.176.1.53 > 86.126.136.56.62419: 34785*- 1/6/9 A 200.33.111.2 (315)
2016-06-29 14:09:01.762201 IP 200.94.176.1.53 > 86.126.136.56.42727: 29794*- 0/1/1 (100)
2016-06-29 14:09:01.799284 IP 200.3.13.11.53 > 86.126.136.56.11313: 44928- 0/5/1 (478)
2016-06-29 14:09:01.800663 IP 86.126.136.56.23374 > 192.36.148.17.53: 7757% [1au] A? LAUTA.UNE.NET.CO. (45)
2016-06-29 14:09:01.800871 IP 86.126.136.56.65302 > 192.36.148.17.53: 47670% [1au] A? NSBOG01.UNE.NET.CO. (47)
2016-06-29 14:09:01.801023 IP 86.126.136.56.8396 > 192.36.148.17.53: 9732% [1au] A? BIRLOCHA.UNE.NET.CO. (48)
2016-06-29 14:09:01.801164 IP 86.126.136.56.42509 > 192.36.148.17.53: 36287% [1au] AAAA? NSBOG01.UNE.NET.CO. (47)
2016-06-29 14:09:01.801353 IP 86.126.136.56.36753 > 192.36.148.17.53: 65478% [1au] AAAA? BIRLOCHA.UNE.NET.CO. (48)
2016-06-29 14:09:01.801627 IP 86.126.136.56.28490 > 192.36.148.17.53: 33558% [1au] AAAA? LAUTA.UNE.NET.CO. (45)
2016-06-29 14:09:01.805754 IP 192.36.148.17.53 > 86.126.136.56.23374: 7757- 0/9/13 (666)
2016-06-29 14:09:01.805760 IP 192.36.148.17.53 > 86.126.136.56.65302: 47670- 0/9/13 (668)
2016-06-29 14:09:01.805986 IP 192.36.148.17.53 > 86.126.136.56.8396: 9732- 0/9/13 (669)
2016-06-29 14:09:01.805989 IP 192.36.148.17.53 > 86.126.136.56.28490: 33558- 0/9/13 (666)
2016-06-29 14:09:01.806089 IP 192.36.148.17.53 > 86.126.136.56.36753: 65478- 0/9/13 (669)
2016-06-29 14:09:01.806091 IP 192.36.148.17.53 > 86.126.136.56.42509: 36287- 0/9/13 (668)
2016-06-29 14:09:01.807188 IP 86.126.136.56.36051 > 156.154.105.25.53: 24598% [1au] A? NSBOG01.UNE.NET.CO. (47)
2016-06-29 14:09:01.807623 IP 86.126.136.56.27519 > 156.154.104.25.53: 17031% [1au] A? BIRLOCHA.UNE.NET.CO. (48)
2016-06-29 14:09:01.807853 IP 86.126.136.56.28163 > 156.154.104.25.53: 64211% [1au] AAAA? NSBOG01.UNE.NET.CO. (47)
2016-06-29 14:09:01.808482 IP 86.126.136.56.51503 > 156.154.104.25.53: 5543% [1au] AAAA? LAUTA.UNE.NET.CO. (45)
2016-06-29 14:09:01.808713 IP 86.126.136.56.58860 > 156.154.104.25.53: 52587% [1au] AAAA? BIRLOCHA.UNE.NET.CO. (48)
2016-06-29 14:09:01.809093 IP 86.126.136.56.24033 > 156.154.105.25.53: 54166% [1au] A? LAUTA.UNE.NET.CO. (45)
2016-06-29 14:09:01.821335 IP 196.216.2.1.53 > 86.126.136.56.23890: 32777*- 2/8/9 AAAA 2001:500:14:6100:ad::1, RRSIG (1352)
2016-06-29 14:09:01.821833 IP 196.216.2.1.53 > 86.126.136.56.53650: 13259*- 2/8/9 A 204.61.216.100, RRSIG (1340)
2016-06-29 14:09:01.844459 IP 156.154.105.25.53 > 86.126.136.56.36051: 24598- 0/5/4 (375)
2016-06-29 14:09:01.845481 IP 86.126.136.56.56438 > 200.13.224.3.53: 50667% [1au] A? NSBOG01.UNE.NET.CO. (47)
2016-06-29 14:09:01.849028 IP 156.154.104.25.53 > 86.126.136.56.28163: 64211- 0/5/4 (375)
2016-06-29 14:09:01.849268 IP 156.154.104.25.53 > 86.126.136.56.58860: 52587- 0/5/4 (376)
2016-06-29 14:09:01.849880 IP 86.126.136.56.17756 > 200.13.224.3.53: 5400% [1au] AAAA? NSBOG01.UNE.NET.CO. (47)
2016-06-29 14:09:01.850120 IP 86.126.136.56.5035 > 200.13.224.3.53: 39708% [1au] AAAA? BIRLOCHA.UNE.NET.CO. (48)
2016-06-29 14:09:01.850484 IP 156.154.105.25.53 > 86.126.136.56.24033: 54166- 0/5/4 (373)
2016-06-29 14:09:01.850833 IP 156.154.104.25.53 > 86.126.136.56.51503: 5543- 0/5/4 (373)
2016-06-29 14:09:01.851248 IP 86.126.136.56.34206 > 200.13.224.3.53: 64569% [1au] A? LAUTA.UNE.NET.CO. (45)
2016-06-29 14:09:01.851866 IP 86.126.136.56.48668 > 200.13.224.3.53: 26387% [1au] AAAA? LAUTA.UNE.NET.CO. (45)
2016-06-29 14:09:01.852255 IP 156.154.104.25.53 > 86.126.136.56.27519: 17031- 0/5/4 (376)
2016-06-29 14:09:01.853003 IP 86.126.136.56.35077 > 200.13.224.3.53: 21697% [1au] A? BIRLOCHA.UNE.NET.CO. (48)
2016-06-29 14:09:02.062013 IP 200.13.224.3.53 > 86.126.136.56.56438: 50667*- 1/3/6 A 200.31.208.100 (236)
2016-06-29 14:09:02.063080 IP 86.126.136.56.45592 > 200.13.224.2.53: 36890% [1au] PTR? 153.192.133.181.in-addr.arpa. (57)
2016-06-29 14:09:02.065873 IP 200.13.224.3.53 > 86.126.136.56.17756: 5400*- 1/3/6 AAAA 2800:e1:111b::2 (236)
2016-06-29 14:09:02.066025 IP 200.13.224.3.53 > 86.126.136.56.5035: 39708*- 1/3/6 AAAA 2800:e1:411b::3 (236)
2016-06-29 14:09:02.066152 IP 200.13.224.3.53 > 86.126.136.56.35077: 21697*- 1/3/6 A 200.13.224.3 (236)
2016-06-29 14:09:02.067832 IP 200.13.224.3.53 > 86.126.136.56.34206: 64569*- 1/3/6 A 200.13.224.2 (236)
2016-06-29 14:09:02.073412 IP 200.13.224.3.53 > 86.126.136.56.48668: 26387*- 1/3/6 AAAA 2800:e1:411b::2 (236)
2016-06-29 14:09:02.286997 IP 200.13.224.2.53 > 86.126.136.56.45592: 36890*- 1/2/5 PTR cable-181-133-192-153.une.net.co. (234)
2016-06-29 14:09:02.288782 IP 86.126.136.56.36652 > 192.36.148.17.53: 53569% [1au] NS? . (28)
2016-06-29 14:09:02.289196 IP 86.126.136.56.64873 > 192.36.148.17.53: 53831% [1au] DS? 181.in-addr.arpa. (45)
2016-06-29 14:09:02.294980 IP 192.36.148.17.53 > 86.126.136.56.36652: 53569*- 14/0/25 NS m.root-servers.net., NS h.root-servers.net., NS k.root-servers.net., NS l.root-servers.net., NS f.root-servers.net., NS c.root-servers.net., NS e.root-servers.net., NS j.root-servers.net., NS i.root-servers.net., NS b.root-servers.net., NS a.root-servers.net., NS g.root-servers.net., NS d.root-servers.net., RRSIG (913)
2016-06-29 14:09:02.295931 IP 192.36.148.17.53 > 86.126.136.56.64873: 53831- 0/10/13 (729)
2016-06-29 14:09:02.296913 IP 86.126.136.56.53900 > 193.0.9.1.53: 63942% [1au] DS? 181.in-addr.arpa. (45)
2016-06-29 14:09:02.349502 IP 193.0.9.1.53 > 86.126.136.56.53900: 63942*- 3/0/1 DS, DS, RRSIG (304)
2016-06-29 14:09:02.351264 IP 86.126.136.56.34859 > 203.119.86.101.53: 14109% [1au] DS? 133.181.in-addr.arpa. (49)
2016-06-29 14:09:02.563007 IP 203.119.86.101.53 > 86.126.136.56.34859: 14109- 0/11/1 (521)
2016-06-29 14:09:02.564301 IP 86.126.136.56.25254 > 193.0.9.11.53: 45924% [1au] DS? 133.181.in-addr.arpa. (49)
2016-06-29 14:09:02.644702 IP 193.0.9.11.53 > 86.126.136.56.25254: 45924*- 0/4/1 (759)
2016-06-29 14:09:02.645698 IP 86.126.136.56.10936 > 199.212.0.53.53: 18614% [1au] DNSKEY? 181.in-addr.arpa. (45)
2016-06-29 14:09:02.764713 IP 199.212.0.53.53 > 86.126.136.56.10936: 18614*- 4/0/1 DNSKEY, DNSKEY, RRSIG, RRSIG (1205)
2016-06-29 14:09:02.769321 IP 86.126.136.56.45733 > 200.31.208.100.53: 23471% [1au] A? cable-181-133-192-153.une.net.co. (61)
2016-06-29 14:09:02.983447 IP 200.31.208.100.53 > 86.126.136.56.45733: 23471 NXDomain*- 0/1/1 (108)
2016-06-29 14:09:02.984610 IP 86.126.136.56.40030 > 192.36.148.17.53: 45942% [1au] DS? co. (31)
2016-06-29 14:09:02.989358 IP 192.36.148.17.53 > 86.126.136.56.40030: 45942*- 3/0/1 DS, DS, RRSIG (274)
2016-06-29 14:09:02.990797 IP 86.126.136.56.38701 > 192.36.148.17.53: 38572% [1au] DS? net.co. (35)
2016-06-29 14:09:02.995731 IP 192.36.148.17.53 > 86.126.136.56.38701: 38572- 0/9/13 (656)
2016-06-29 14:09:02.997513 IP 86.126.136.56.31230 > 156.154.101.25.53: 21107% [1au] DS? net.co. (35)
2016-06-29 14:09:03.028904 IP 156.154.101.25.53 > 86.126.136.56.31230: 21107*- 0/4/1 (465)
2016-06-29 14:09:03.029846 IP 86.126.136.56.19070 > 156.154.100.25.53: 30032% [1au] DNSKEY? co. (31)
2016-06-29 14:09:03.064164 IP 156.154.100.25.53 > 86.126.136.56.19070: 30032*- 5/0/1 DNSKEY, DNSKEY, DNSKEY, DNSKEY, RRSIG (1169)
2016-06-29 14:09:03.066762 IP 86.126.136.56.9355 > 156.154.102.25.53: 59011% [1au] DS? une.net.co. (39)
2016-06-29 14:09:03.097511 IP 156.154.102.25.53 > 86.126.136.56.9355: 59011*- 0/4/1 (476)
2016-06-29 14:09:16.514752 IP 86.126.136.56.11267 > 192.33.14.30.53: 45529% [1au] TXT? verstrepen.net. (43)
2016-06-29 14:09:16.553695 IP 192.33.14.30.53 > 86.126.136.56.11267: 45529- 0/9/6 (720)
2016-06-29 14:09:16.554552 IP 86.126.136.56.63715 > 192.42.93.30.53: 60033% [1au] A? dns1.name-services.com. (51)
2016-06-29 14:09:16.554642 IP 86.126.136.56.17643 > 192.42.93.30.53: 10301% [1au] A? dns2.name-services.com. (51)
2016-06-29 14:09:16.554692 IP 86.126.136.56.22565 > 192.42.93.30.53: 12831% [1au] A? dns3.name-services.com. (51)
2016-06-29 14:09:16.554749 IP 86.126.136.56.56904 > 192.42.93.30.53: 35517% [1au] A? dns4.name-services.com. (51)


Edited by caracal, 29 June 2016 - 13:11.


#8
caracal

caracal

    Junior Member

  • Grup: Members
  • Posts: 226
  • Înscris: 30.01.2007
Mi-e si rusine. Am sunat si la RDS. Problema a fost aiureala mea. La un moment dat mutandu-ma in alta parte, mi s-a alocat alt IP static. Pe serverul slave am uitat sa modific IP-ul serverului master cu cel noi alocat. Probabil cat a mers, a fost fost datorita cache-ului.

Anunturi

Chirurgia endoscopică a hipofizei Chirurgia endoscopică a hipofizei

"Standardul de aur" în chirurgia hipofizară îl reprezintă endoscopia transnazală transsfenoidală.

Echipa NeuroHope este antrenată în unul din cele mai mari centre de chirurgie a hipofizei din Europa, Spitalul Foch din Paris, centrul în care a fost introdus pentru prima dată endoscopul în chirurgia transnazală a hipofizei, de către neurochirurgul francez Guiot. Pe lângă tumorile cu origine hipofizară, prin tehnicile endoscopice transnazale pot fi abordate numeroase alte patologii neurochirurgicale.

www.neurohope.ro

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Forumul Softpedia foloseste "cookies" pentru a imbunatati experienta utilizatorilor Accept
Pentru detalii si optiuni legate de cookies si datele personale, consultati Politica de utilizare cookies si Politica de confidentialitate