Document toolboxDocument toolbox

Troubleshooting0

Owned by S (Deactivated)
07 Sept 2017
1 min read

Resolving DNS

 The BankID Server must be able to resolve the following DNS names depending on the environment:

Internet

DNS

Internet IP address

services-preprod.bankid.no

91.102.24.82

va-preprod1.bankid.no

91.102.24.76

sdm-preprod.bankid.no

91.102.24.84

services.bankid.no

91.102.25.100

va1.bankid.no

91.102.24.134

sdm.bankid.no

91.102.25.50

 Table 14 – Internet DNS names and IP addresses

Extranet

DNS

Extranet IP address

sdm-preprod.bankid.no

91.102.24.209

sdm.bankid.no

91.102.25.163

services-preprod.bankid.no

91.102.24.241

services.bankid.no

91.102.25.220

va1.bankid.no

91.102.26.110

va-preprod1.bankid.no

91.102.24.225

 Table 15 – Extranet DNS names and IP addresses 

Client proxy

Merchants must allow for requests from the Client proxy:

DNS

Internet IP address

https://cp-preprod.bankid.no/clientproxy

91.102.27.1 (public address)

https://cp.bankid.no/clientproxy

91.102.25.68 (public address)

Table 16 – Client proxy DNS names and IP addresses

Also note that if the Web-client detects any of the following error codes when communicating with the Client proxy, the handleError() request from the client will be sent directly to the merchantURL set in the initSession() request:

  • BID-20C1 - PROXY_COMMUNICATION_ERROR1
  • BID-20C4 - PROXY_COMMUNICATION_TIMEOUT
  • BID-20C5 - PROXY_COMMUNICATION_ABORT

This means that the merchantURL must be accessible for the Web-client even though a Client proxy is in use, see also 3.2.3.

1 See [BEMEC].