Use 'dig' to Resolve DNS Issues
Use 'dig' to Resolve DNS Issues
🔍 What the dig results mean
root@your-server:~# dig router.huggingface.co @1.1.1.1
; <<>> DiG 9.20.11-1ubuntu2.1-Ubuntu <<>> router.huggingface.co @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27395
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;router.huggingface.co. IN A
;; ANSWER SECTION:
router.huggingface.co. 60 IN A 108.159.61.60
router.huggingface.co. 60 IN A 108.159.61.8
router.huggingface.co. 60 IN A 108.159.61.109
router.huggingface.co. 60 IN A 108.159.61.104
;; Query time: 237 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Mon Dec 08 07:30:36 UTC 2025
;; MSG SIZE rcvd: 114
root@your-server:~# dig router.huggingface.co @8.8.8.8
; <<>> DiG 9.20.11-1ubuntu2.1-Ubuntu <<>> router.huggingface.co @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47260
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;router.huggingface.co. IN A
;; ANSWER SECTION:
router.huggingface.co. 60 IN A 108.159.46.68
router.huggingface.co. 60 IN A 108.159.46.36
router.huggingface.co. 60 IN A 108.159.46.6
router.huggingface.co. 60 IN A 108.159.46.121
;; Query time: 29 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Mon Dec 08 07:31:23 UTC 2025
;; MSG SIZE rcvd: 114
- Cloudflare (1.1.1.1) resolves router.huggingface.co correctly.
- Google (8.8.8.8) resolves router.huggingface.co correctly.
So the domain is NOT blocked on the internet.
The ONLY resolver that fails is Hostinger's default DNS.
That means Hostinger intercepts or overrides DNS on your VPS unless you override it system-wide.
This is why:
- Proxmox (your own infra) → OK
- Hostinger → ❌ only that subdomain
This is classic AI routing filtering.
Solution: Fix Hostinger VPS; DNS Filtering & Enable DNS over TLS