Nod32 update servers - what should they be?

Discussion in 'NOD32 version 2 Forum' started by ROAMER, Oct 3, 2005.

Thread Status:
Not open for further replies.
  1. ROAMER

    ROAMER Registered Member

    Joined:
    Oct 3, 2005
    Posts:
    1
    In my list I have the following..

    u1.eset.com
    u3.eset.com
    u4.eset.com
    u7.eset.com
    82.165.250.33
    82.165.237.14
    J:nod_upd\

    The ones that concern me is the ip addressed ones ..
    whois info is some US/German site .. :eek: (see below)

    Is this another eset mirror .. if not how do I get rid of it .. and more importantly how did it get into the list?

    Cheers


     
  2. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Welcome to Wilders Roamer.

    The servers you have listed are all fine, it is best to leave the server to "Choose Automatically".

    Cheers :D
     
  3. RejZoR

    RejZoR Registered Member

    Joined:
    May 31, 2004
    Posts:
    6,426
    The IP servers are just in case for times when DNS may fail.
    Happened twice not long ago... Direct server IP is of course not affected by DNS problems...
     
  4. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    eset has also changed it's DNS from the provider used when failure became an issue, to lanechange.com - who at least have 3 different netblocks for the nameservers listed on the Eset.com domain:

    NS1.LANECHANGE.NET 64.40.110.35
    NS2.LANECHANGE.NET 198.96.220.161
    NS3.LANECHANGE.NET 209.15.85.1

    this is to be recommended for ALL names, and is why I've recently changed our nameservers to use two different physical NOCs for redundancy - no more putting all the eggs in a single basket for me... or Eset! ;)
     
Thread Status:
Not open for further replies.