I’m working on a Node.js web application that integrates with Hugging Face's API for fine-tuning models. However, I’ve encountered a DNS resolution issue where I’m unable to resolve the domain api.huggingface.co.
I have already:
Updated /etc/resolv.conf to use Google’s DNS servers (8.8.8.8 and 8.8.4.4).Flushed the DNS cache.Restarted the Network Manager.Despite these efforts, I'm still getting the error "No address associated with hostname" when pinging api.huggingface.co. Additionally, tools like dig and nslookup return no answer for the domain.
Steps Taken:Updated /etc/resolv.conf with:bash
nameserver 8.8.8.8nameserver 8.8.4.4Restarted NetworkManager and flushed DNS caches:bash
sudo systemctl restart NetworkManagerRan the following commands:bash
dig api.huggingface.conslookup api.huggingface.coBoth dig and nslookup fail to return a valid IP for api.huggingface.co, and I’m unsure how to proceed further.
Environment Details:OS: Ubuntu 24.04Node.js Version: 18.19.1Network: Local (tested via Ethernet)Relevant Code Files in GitHub Repository:Backend Logic:
server.js: Contains the logic for Hugging Face API interactions and error handling (/backend/server.js).jobs.js, fineTuningQueue.js: Manages the job queue and handles model fine-tuning processes (/backend/models).Frontend:
dashboard.ejs: Handles UI for displaying job statuses (/frontend/views/dashboard.ejs).settings.ejs: Manages Hugging Face token input and submission (/frontend/views/settings.ejs).Content Security Policy (CSP):
CSP configuration within server.js (/backend/server.js).Database Management:
db.js, Job.js: Manages database interactions and job status transitions (/backend/db.js, /backend/models/Job.js).What I Expected:I expected ping, dig, and nslookup to resolve the domain and return a valid IP address for api.huggingface.co.
Question:What could be causing this DNS resolution issue, and what steps should I take to resolve it?