DNS broken on login-2

[DanDaMan]

DevCloud ssh seems to be working again, but DNS seems to be broken on login-2:

uXXXXXX@login-2:~$ nslookup www.google.com
Server:         127.0.0.53
Address:        127.0.0.53#53

** server can't find www.google.com: SERVFAIL

 a workaround is to use an interactive node (qsub -I), but it seems wasteful, and in my experience can have less external bandwidth.

uXXXXXX@s001-n058:~$ nslookup www.google.com
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   www.google.com
Address: 142.251.33.36
Name:   www.google.com
Address: 2607:f8b0:4000:80e::2004

[Rahila_T_Intel · Accepted solution]

Hi,

Thank you for posting in Intel Communities.

For your information, login node uses a lightweight general-purpose processor. Login nodes should not be used for development or execution of programs. It is an interface node that helps to connect or submit jobs to compute nodes.

As you already know, we can use compute nodes to download or clone repositories.

However, the downloaded files would be available in the cloud, so you can access them in login node and compute node as well.

From the above diagram, we could see that HTTPS cannot be accessed via login node.

Thank you for your feedback. We have provided your feedback to the relevant team.

Thanks

[Rahila_T_Intel]

Hi,

Please be informed that DevCloud does not allow external website access from the login node. External access is allowed only from compute nodes.

If this clarifies your query, make sure to accept this as a solution. This would help others with similar query.

Please let me know if we can go ahead and close this case?

Thanks

[DanDaMan]

Yes, feel free to close it. Thanks for the information!

[Rahila_T_Intel]

Hi,

Glad to know that your issue is resolved. 

Thanks for accepting our solution. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

Thanks