mitzone
-
Posts
3 -
Joined
-
Last visited
Posts posted by mitzone
-
-
Hello,
Any issues on your side ESET?
I have problems activating clients. Here's a snip from my proxy error log:
[Mon Mar 30 17:49:43.635202 2020] [proxy_connect:error] [pid 4192:tid 12800] (OS 11001)No such host is known. : [client 10.1.4.1:50156] AH02327: failed to resolve hostname 'edf.eset.com'
[Mon Mar 30 17:49:43.635202 2020] [proxy:error] [pid 4192:tid 12800] [client 10.1.4.1:50156] AH00898: DNS lookup failure for: edf.eset.com returned by edf.eset.com:443
[Mon Mar 30 17:50:11.620554 2020] [proxy_connect:error] [pid 4192:tid 12800] (OS 11001)No such host is known. : [client 10.1.4.1:50158] AH02327: failed to resolve hostname 'edf.eset.com'Any ETA on fixing this?
Cheers,
Mihai.
-
Thanks,
Had the same issue on a brand new install. Weird to have this issue on a brand new install right ESET?
Activation failure
in ESET PROTECT On-prem (Remote Management)
Posted
===== This is from querying one of the biggest provider in Romania.
dig edf.eset.com @193.231.236.25
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> edf.eset.com @193.231.236.25
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8535
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;edf.eset.com. IN A
;; ANSWER SECTION:
edf.eset.com. 613 IN CNAME edf.wip.eset.com.
;; AUTHORITY SECTION:
wip.eset.com. 2039 IN SOA h3-f5lb01-s.eset.com. sysadmin.eset.com. 2012012879 10800 3600 604800 86400
;; Query time: 1 msec
;; SERVER: 193.231.236.25#53(193.231.236.25)
;; WHEN: Mon Mar 30 19:17:22 EEST 2020
;; MSG SIZE rcvd: 120
==== This is from querying CF
dig edf.eset.com @1.1.1.1
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> edf.eset.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39396
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;edf.eset.com. IN A
;; ANSWER SECTION:
edf.eset.com. 592 IN CNAME edf.wip.eset.com.
edf.wip.eset.com. 33 IN CNAME edfpcs.trafficmanager.net.
edfpcs.trafficmanager.net. 3 IN CNAME bal-edf-pcs-app-vmss-01.westus.cloudapp.azure.com.
bal-edf-pcs-app-vmss-01.westus.cloudapp.azure.com. 9 IN A 13.64.117.133
;; Query time: 1 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Mar 30 19:18:14 EEST 2020
;; MSG SIZE rcvd: 181
The dns resolvers from RO (tried 2 ISPs) are returning edf.wip.eset.com as CNAME for some reason, while the CF one is returning the correct entries.
If you use split horizon or country/region based resolvers, something screwd up in your config.
I resolved my issue by putting a static entry for the moment.
Cheers,
Mihai.