Overview

DNS Science provides free public DNS resolvers that combine enterprise-grade security features with Web3 domain resolution. Our caches filter malicious domains, block known threats, and seamlessly resolve blockchain-based domains like .eth, .sol, and .crypto - all without requiring browser extensions or special software.

Threat Intelligence

Real-time blocking of malware, phishing, and C2 domains

Web3 Resolution

Native support for ENS (.eth), SNS (.sol), and Unstoppable Domains

Privacy Focused

No logging of individual queries, aggregated stats only

High Availability

4 geographically distributed cache servers

DNS Server Addresses

Use any of our cache servers for redundancy. We recommend configuring at least two servers.

cache01.dnsscience.io

129.213.88.204

Primary - US East

cache02.dnsscience.io

150.136.215.50

Secondary - US East

cache03.dnsscience.io

150.136.219.61

Tertiary - US East

cache04.dnsscience.io

129.213.25.48

Quaternary - US East

Supported Web3 TLDs

TLD	Provider	Blockchain
`.eth`	Ethereum Name Service (ENS)	Ethereum
`.sol`	Solana Name Service (SNS/Bonfida)	Solana
`.crypto`	Unstoppable Domains	Polygon
`.wallet`	Unstoppable Domains	Polygon
`.nft`	Unstoppable Domains	Polygon
`.x`	Unstoppable Domains	Polygon
`.blockchain`	Unstoppable Domains	Polygon
`.dao`	Unstoppable Domains	Polygon

Quick Setup Guide

Select your operating system below for setup instructions:

# Run PowerShell as Administrator

# Set DNS for all network adapters
Get-NetAdapter | Where-Object {$_.Status -eq "Up"} | ForEach-Object {
    Set-DnsClientServerAddress -InterfaceIndex $_.ifIndex -ServerAddresses ("129.213.88.204","150.136.215.50")
}

# Verify the change
Get-DnsClientServerAddress -AddressFamily IPv4

# Test Web3 resolution
Resolve-DnsName vitalik.eth

# To revert to DHCP-assigned DNS:
# Get-NetAdapter | Where-Object {$_.Status -eq "Up"} | ForEach-Object {
#     Set-DnsClientServerAddress -InterfaceIndex $_.ifIndex -ResetServerAddresses
# }

GUI Alternative

Open Settings > Network & Internet > Change adapter options, right-click your connection, select Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties, and enter the DNS addresses manually.

# Set DNS for Wi-Fi (most common)
sudo networksetup -setdnsservers Wi-Fi 129.213.88.204 150.136.215.50

# Set DNS for Ethernet (if using wired connection)
sudo networksetup -setdnsservers Ethernet 129.213.88.204 150.136.215.50

# Flush DNS cache to apply changes immediately
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

# Verify the change
networksetup -getdnsservers Wi-Fi

# Test Web3 resolution
dig vitalik.eth

# To revert to DHCP-assigned DNS:
# sudo networksetup -setdnsservers Wi-Fi "Empty"

List Available Network Services

Run networksetup -listallnetworkservices to see all available network interfaces on your Mac.

# Method 1: Using systemd-resolved (Ubuntu 18.04+)

# Edit resolved.conf
sudo tee /etc/systemd/resolved.conf.d/dnsscience.conf > /dev/null << 'EOF'
[Resolve]
DNS=129.213.88.204 150.136.215.50
FallbackDNS=150.136.219.61 129.213.25.48
DNSSEC=allow-downgrade
DNSOverTLS=opportunistic
EOF

# Restart systemd-resolved
sudo systemctl restart systemd-resolved

# Verify the change
resolvectl status

# Test Web3 resolution
dig vitalik.eth

# --------------------------------------------------------
# Method 2: Using /etc/resolv.conf directly (older systems)
# --------------------------------------------------------

# Disable systemd-resolved if present
# sudo systemctl disable systemd-resolved
# sudo systemctl stop systemd-resolved

# Edit resolv.conf
sudo tee /etc/resolv.conf > /dev/null << 'EOF'
nameserver 129.213.88.204
nameserver 150.136.215.50
EOF

# Prevent NetworkManager from overwriting
sudo chattr +i /etc/resolv.conf

# To unlock: sudo chattr -i /etc/resolv.conf

NetworkManager Users

If using NetworkManager, you may need to configure DNS via nmcli or the GUI to prevent automatic DNS overwrites.

# Method 1: Using nmcli (NetworkManager)

# Get your connection name
nmcli connection show

# Set DNS (replace 'Wired connection 1' with your connection name)
sudo nmcli connection modify "Wired connection 1" ipv4.dns "129.213.88.204 150.136.215.50"
sudo nmcli connection modify "Wired connection 1" ipv4.ignore-auto-dns yes

# Restart the connection
sudo nmcli connection down "Wired connection 1"
sudo nmcli connection up "Wired connection 1"

# Verify
cat /etc/resolv.conf

# Test Web3 resolution
dig vitalik.eth

# --------------------------------------------------------
# Method 2: Edit ifcfg file directly (legacy)
# --------------------------------------------------------

# Find your network interface config
ls /etc/sysconfig/network-scripts/ifcfg-*

# Edit the config (e.g., ifcfg-eth0)
sudo tee -a /etc/sysconfig/network-scripts/ifcfg-eth0 > /dev/null << 'EOF'
DNS1=129.213.88.204
DNS2=150.136.215.50
PEERDNS=no
EOF

# Restart networking
sudo systemctl restart NetworkManager

# To revert:
# sudo nmcli connection modify "Wired connection 1" ipv4.ignore-auto-dns no
# sudo nmcli connection modify "Wired connection 1" ipv4.dns ""

Testing Your Configuration

After configuring DNS, verify everything is working:

# Test standard DNS resolution
dig google.com

# Test Web3 domain resolution (ENS)
dig vitalik.eth

# Test Solana Name Service
dig bonfida.sol

# Check which DNS server answered
dig +short google.com @129.213.88.204

API Access

Want programmatic access to our Web3 resolution? Use our REST API:

# Resolve an ENS domain
curl https://dnsscience.io/api/v2/web3/resolve/vitalik.eth

# Check domain availability
curl https://dnsscience.io/api/v2/web3/check/myname.eth

# Get supported TLDs
curl https://dnsscience.io/api/v2/web3/tlds

Threat Intelligence Features

Our DNS caches automatically protect against:

Malware Domains - Known command & control servers and malware distribution sites
Phishing Sites - Domains identified in active phishing campaigns
DGA Domains - Algorithmically generated domains used by botnets
Cryptojacking - Mining scripts and associated infrastructure
Newly Registered Domains - Optional blocking of domains less than 30 days old

Privacy Policy

DNS Science public caches are designed with privacy in mind:

No individual query logging - we only collect aggregated statistics
No selling of DNS data to third parties
No DNS-based user profiling or tracking
Queries are processed in memory and discarded

Support & Feedback

Having issues or want to suggest improvements?

Open a support ticket at dnsscience.io/tickets
Email: support@dnsscience.io
Check service status at dnsscience.io/status