Debugging DNS Resolution for rubenflamshepherd.com Domain
269 messages · Page 5 of 14
Nameservers are correctly set. Let me query Porkbun's nameservers directly and check your local DNS.
Tool: Bash
$ dig A rubenflamshepherd.com @maceio.ns.porkbun.com +shortTool: Bash
$ scutil --dns | grep "nameserver" | head -5Tool: Bash
$ dig A rubenflamshepherd.com +shortThe issue is your local DNS servers. Porkbun and Google DNS resolve it fine, but your local DNS (66.207.192.6) returns nothing.
Tool: Bash
$ dig A rubenflamshepherd.com @66.207.192.6 +shortFound it. Your ISP's DNS server (66.207.192.6) is not resolving the domain, but Google DNS and Porkbun's nameservers work fine.
Quick fix - flush your local DNS cache:
Tool: Bash
$ sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder && echo "DNS cache flushed"I can't run sudo. Try this manually in your terminal:
```bash
sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
```
Or the issue is your ISP's DNS server itself. You could temporarily switch to Google DNS (8.8.8.8) in System Settings > Network > DNS to verify.
The domain **is** resolving correctly on public DNS - it's just your local ISP DNS that's having trouble. This could be:
1. A propagation delay at your ISP's DNS
2. A caching issue on their end
3. Something blocking at the ISP level
Want me to check anything else, or would you like to try flushing your DNS cache first?
I ran it locally on my cli, continue