server IP address could not be found

[charles_penabur_it]

please help, i cannot access bpjsketenagakerjaan.go.id or https://www.bpjsketenagakerjaan.go.id when using OpenDns as DNS, when i change the DNS to Google DNS i can access the site .

[rotblitz]

In case you're using the OpenDNS data center in Sao Paolo, raise a support ticket with OpenDNS, link "Submit a request" above.

Else copy & paste the complete plain text output of the following diagnostic commands to here:

nslookup -type=txt debug.opendns.com.
nslookup www.bpjsketenagakerjaan.go.id.

 As a temporary workaround you can add the following line to your local hosts file:

103.82.6.10 bpjsketenagakerjaan.go.id www.bpjsketenagakerjaan.go.id

[charles_penabur_it]

hi rotblitz,

I already submitted a ticket and the support team replied something wrong with my router firewall settings, i just don't know where's the wrong one, because i only setting 2 rules to force user using OpenDNS. 

and thank you for the temporary solution, it's works well, i just need to apply it to about 30 more routers . 

please help me, i need permanent solution for this issue.

Below is diagnostic result for lookup bpjsketenagakerjaan.go.id

Results for: nslookup bpjsketenagakerjaan.go.id. 208.67.220.220
stdout:
Server:  resolver2.opendns.com
Address:  208.67.220.220
DNS request timed out.
    timeout was 2 seconds.

Results for: nslookup bpjsketenagakerjaan.go.id. 4.2.2.1
stdout:
Server:  a.resolvers.level3.net
Address:  4.2.2.1
DNS request timed out.
    timeout was 2 seconds.

[rotblitz]

"I already submitted a ticket"

You should have referred them to their CacheCheck results for this domain from https://cachecheck.opendns.com/

"i just need to apply it to about 30 more routers ."

I merely thought this tweak to be applied on computers.

DNS request timed out.
    timeout was 2 seconds.

These response timeouts from different DNS services (OpenDNS and Level-3) are most likely "because i only setting 2 rules to force user using OpenDNS".  If you have such rules, you cannot specify a DNS server address in the command as you did.  Instead you must use your router's private IP address, implicitly or explicitly, else the DNS lookups will be blocked by your rules, leading to these timeouts.

Post now the outputs of these diagnostic commands (not any other variations as you did before):

nslookup -timeout=12 -type=txt debug.opendns.com.
nslookup -timeout=12 www.bpjsketenagakerjaan.go.id.
tracert 208.67.222.222
tracert 208.67.220.220