Skip to main content

Domain & Nameserver Configuration

Our Nameservers​

Primary (ns1): ns1.alfieweb.com
Secondary (ns2): ns2.alfieweb.com

Client Instructions​

When clients need to point their domain to our hosting, provide these instructions:

If Client Owns Domain Elsewhere​

Step 1: Login to Domain Registrar

  • Client logs into where they purchased domain (Namecheap, GoDaddy, etc.)

Step 2: Find Nameserver Settings

  • Look for: "Nameservers", "DNS Settings", or "Domain Settings"
  • Each registrar has different interface

Step 3: Change Nameservers

  • Replace existing nameservers with:
    • ns1.alfieweb.com
    • ns2.alfieweb.com
  • Save changes

Step 4: Wait for Propagation

  • Typical time: 2-24 hours
  • Maximum time: 48 hours
  • Can check status at: whatsmydns.net
Propagation Time

Always inform clients that DNS changes take time. Most propagate within a few hours, but allow up to 48 hours to be safe.

For Team: Domain Setup Procedures​

Scenario 1: Client Has External Domain​

  1. Provide nameserver details in welcome email
  2. Add domain to DirectAdmin (it will be in parking mode until DNS propagates)
  3. Set up DNS zone in DirectAdmin
  4. Verify propagation after 24-48 hours

Scenario 2: We Register Domain for Client​

  1. Register domain through our registrar
  2. Immediately set nameservers to our NS servers
  3. Add to DirectAdmin
  4. Configure DNS zone
  5. Usually propagates within 2-4 hours for new domains

Scenario 3: Client Wants to Keep External DNS​

If client wants to manage DNS elsewhere:

  1. Get server IP address from DirectAdmin
  2. Provide A record details:
    • Record Type: A
    • Host: @ (for root domain)
    • Value: [Server IP]
    • TTL: 3600 or Auto
  3. For www subdomain:
    • Record Type: A or CNAME
    • Host: www
    • Value: [Server IP] or @
  4. For email (MX records) - see Email documentation

Checking DNS Propagation​

Tools to Use​

  • whatsmydns.net - Check global DNS propagation
  • dnschecker.org - Alternative DNS lookup tool
  • Terminal/CMD: nslookup domain.com or dig domain.com

What to Check​

# Check nameservers
nslookup -type=NS domain.com

# Check A record
nslookup domain.com

# Should return our nameservers and server IP

Common DNS Issues​

Domain Not Resolving​

Causes:

  • DNS not propagated yet (wait longer)
  • Incorrect nameserver spelling
  • Domain not added to DirectAdmin
  • Server firewall blocking

Solution:

  1. Verify nameservers set correctly at registrar
  2. Check domain exists in DirectAdmin
  3. Wait full 48 hours if recent change
  4. Verify DNS zone configured correctly

Website Shows "Server Not Found"​

Causes:

  • DNS not propagated
  • A record pointing to wrong IP
  • Server down

Solution:

  1. Check DNS propagation status
  2. Verify A record shows correct server IP
  3. Ping server IP to confirm it's responding
  4. Check DirectAdmin server status

Email Works But Website Doesn't (or vice versa)​

Cause: Mixed DNS setup - some records at old host, some at new

Solution:

  • Ensure ALL nameservers point to us, OR
  • If using external DNS, verify all required records (A, MX, CNAME) are configured

DNS Zone Configuration in DirectAdmin​

Standard Records We Add​

A Record:
@ → [Server IP]
www → [Server IP]

MX Records:
@ → mail.domain.com (Priority 10)

CNAME Records:
mail → @
ftp → @

TXT Records:
SPF, DKIM, DMARC (for email authentication)

Adding Custom DNS Records​

If client needs custom records:

  1. Login to DirectAdmin reseller panel
  2. Navigate to client account → DNS Management
  3. Click "Add Record"
  4. Select record type (A, CNAME, TXT, etc.)
  5. Enter details provided by client
  6. Save

Registrar-Specific Notes​

Common Registrars​

Namecheap:

  • Domain List → Manage → Domain → Nameservers → Custom DNS

GoDaddy:

  • My Products → Domains → DNS → Nameservers → Change

Google Domains:

  • My Domains → DNS → Name servers → Use custom name servers

Cloudflare:

  • If using Cloudflare DNS, don't change nameservers
  • Instead, update A records to point to our IP
  • Ensure SSL/TLS mode is "Full" or "Full (Strict)"

Support Quick Reference​

Client IssueTeam Action
"How do I change nameservers?"Send registrar-specific guide or generic instructions
"How long does it take?""2-24 hours typically, up to 48 hours maximum"
"Website not working after 48 hours"Check DNS propagation, verify domain in DirectAdmin
"Want to use Cloudflare"Provide server IP, guide to A record setup
"Need custom DNS record"Add via DirectAdmin DNS Management