Access to sitefinder-idn.verisign.com

HCL Domino Domino Forum
1

Hello,

after update to R6 we have outgoing port 1352 traffic fromt the client to the mentioned site sitefinder-idn.verisign.com

does anybody have an idea what this is caused from ?

thanks

2

Subject: access to sitefinder-idn.verisign.com

Could be because of the greedy new policy of Verisign:

3

Subject: RE: access to sitefinder-idn.verisign.com

Thanks,

that might be, but why does the client try to access with port 1352 ?

g.

4

Subject: RE: access to sitefinder-idn.verisign.com

Hypothesis…

You have multiple DNS servers right?

You try an external name server first, then an internal one?

Your clients connect to dominoserver.example.com (where example.com does not exist in the public DNS)?

Before Verisign debacle, the external server would return “host not found” and the lookup would be done on the other server, finding a host in your local network.

Now, the external server will alwways return verisign site finder service when queried for dominoserver.example.com and the Notes client wil attempt to connect to that, using NRPC (port 1352) precisely because it is a Notes client.

I have seen planty of similar reports if things stopping working since the new wildcard DNS A records were put in place on the .com and .net TLDs.

Chris Linfoot