Nameservers play a crucial role in how your domain connects to your website, email, and other online services. This article will help you understand what nameservers are, which ones you should use for your domain, and whether self-hosting nameservers is the right choice for your needs.
What Are Nameservers?
Nameservers are specialised servers that translate human-readable domain names (like example.com) into IP addresses (like 192.0.2.1) that computers use to identify each other on the internet. This system is called the Domain Name System (DNS), and nameservers are a fundamental component of how the internet works.
When someone types your domain name into their browser, their computer first contacts a nameserver to find out where your website is hosted. The nameserver responds with the IP address associated with your domain, allowing the browser to connect to your website.
Information: Nameservers are typically provided as a set of at least two servers (e.g., ns1.example.com and ns2.example.com) to ensure redundancy. If one nameserver fails, the other can continue providing DNS resolution services.
Common DNS Record Types
Before exploring nameserver options, it's helpful to understand the different types of DNS records you might need to configure:
Record Type | Purpose | Example Usage |
A Record | Maps a domain to an IPv4 address | example.com → 192.0.2.1 |
AAAA Record | Maps a domain to an IPv6 address | example.com → 2001:0db8:85a3:0000:0000:8a2e:0370:7334 |
CNAME Record | Creates an alias from one domain to another | www.example.com → example.com |
MX Record | Directs email to a mail server | example.com mail → mail.example.com with priority value |
TXT Record | Stores text information | Used for SPF, DKIM, domain verification |
NS Record | Specifies nameservers for the domain | example.com → ns1.dnshost.com, ns2.dnshost.com |
SRV Record | Defines location of servers for specific services | Used for VoIP, IM, and other services |
CAA Record | Specifies which Certificate Authorities can issue certificates | Restricts which CAs can issue SSL/TLS certificates |
Different DNS providers may offer varying levels of support for these record types, as well as different interfaces for managing them.
Nameserver Options for Your Domain
When setting up a domain, you have several options for nameservers:
BinaryLane Nameservers
BinaryLane provides reliable DNS hosting for domains associated with your BinaryLane services. Our nameservers are:
- ns1.binarylane.com.au
- ns2.binarylane.com.au
- ns3.binarylane.com.au
BinaryLane is also a domain registrar (via our domain wholesaler Synergy). When you register a domain through BinaryLane, our nameservers are set automatically for your convenience.
BinaryLane DNS Features:
- Support for standard DNS record types (A, AAAA, CNAME, MX, TXT, NS, SRV)
- Simple DNS management through mPanel
- Free with BinaryLane accounts
- All DNS records have a 60-minute TTL (Time-To-Live)
Managing BinaryLane DNS Records:
If you choose to use BinaryLane's nameservers for your domain, it's important to understand how to properly manage the DNS records:
- mPanel Management: DNS records for domains using BinaryLane nameservers must be managed through mPanel's DNS management interface
- API Access: Records can also be managed programmatically using the BinaryLane CLI client or the BinaryLane API directly (both requiring a valid API token)
Warning: WHM/cPanel users: If you're using a server with WHM/cPanel, be aware that setting BinaryLane's nameservers within your WHM/cPanel interface will NOT automatically apply those DNS records to BinaryLane's nameservers. You must separately configure your DNS records in BinaryLane's mPanel for them to take effect. Any records configured in WHM/cPanel will only apply if you're using your server's nameservers.
Note: BinaryLane DNS currently does not support DNSSEC. If DNSSEC is required for your domain, you will need to use an alternative DNS provider that offers this feature.
Domain Registrar's Nameservers
Most domain registrars provide their own nameservers that you can use with your domain. These are often the default option when you register a domain.
Advantages:
- Convenience - Already set up and ready to use
- Basic DNS management interface typically included
- Often free with domain registration
Disadvantages:
- May have limited DNS features
- Potentially slower update times
- May not include advanced features like DNSSEC, geo-routing, or detailed analytics
Dedicated DNS Providers
Specialised DNS providers like Cloudflare, Amazon Route 53, or Google Cloud DNS offer advanced DNS management features.
Advantages:
- Typically faster DNS resolution through global networks
- Enhanced reliability with distributed nameserver networks
- Advanced features like load balancing, DDoS protection, and analytics
- Often include performance and security enhancements
Disadvantages:
- Premium features may require paid plans
- More complex setup process
- Possible vendor lock-in with certain features
Self-Hosted Nameservers
Running your own nameservers on servers that you control gives you complete control over your DNS infrastructure.
Warning: Self-hosting nameservers requires significant technical expertise, careful planning, and ongoing maintenance to ensure reliability. DNS failures can make all your services unreachable.
Nameserver Comparison
Here's a comparison of different nameserver options to help you make an informed decision:
Feature | BinaryLane | Typical Registrar | Dedicated DNS Provider | Self-Hosted |
Cost | Free with account | Free with domain | Free to premium tiers | Server costs + maintenance |
Ease of Use | High | Medium-High | Medium | Low |
Update Speed | Medium (60 min TTL) | Medium | Fast | Depends on configuration |
DNSSEC Support | No | Varies | Yes (most providers) | Yes (if configured) |
Global Performance | Good | Varies | Excellent | Depends on infrastructure |
API Access | Yes (CLI & API) | Limited | Comprehensive | Full control |
DDoS Protection | Basic | Basic | Advanced | Depends on configuration |
Technical Expertise Required | Low | Low | Medium | High |
Should You Self-Host Nameservers?
Self-hosting nameservers is an option for businesses or individuals with specific requirements, but it comes with significant responsibilities. Here's what you need to know:
Technical Requirements for Self-Hosting
- Multiple Servers: You ideally need at least two geographically separated servers for redundancy
- Fixed IP Addresses: Stable, static IP addresses for each nameserver
- DNS Software: Software like BIND, PowerDNS, or NSD properly configured and maintained
- Reliable Network: 24/7 network availability with minimal downtime
- Security Measures: Protection against DNS-specific attacks like cache poisoning, reflection attacks, etc.
- Regular Updates: Continuous monitoring and software updates
Key Considerations
- DNS Glue Records: Your domain registrar must support glue records for your self-hosted nameservers
- Technical Expertise: You need significant DNS knowledge to configure and maintain nameservers properly
- Responsibility: You are solely responsible for the availability of your DNS services
- Regulatory Compliance: Some TLDs have specific requirements for nameserver redundancy and availability
Note: For most businesses and individuals, using a reliable third-party DNS provider is more cost-effective and reliable than self-hosting nameservers.
Understanding DNS Propagation
When you make changes to your DNS settings, such as changing nameservers or updating records, the changes don't take effect immediately everywhere. This delay is known as "DNS propagation."
DNS propagation occurs because:
- DNS information is cached at multiple levels across the internet
- Different DNS servers refresh their caches at different times
- Each DNS record has a Time-To-Live (TTL) value that determines how long it should be cached
Typical propagation times:
- Nameserver changes: 24-48 hours (sometimes longer)
- BinaryLane DNS record changes: Up to 60 minutes (all BinaryLane DNS records have a 60-minute TTL)
- Other DNS record changes: Minutes to hours, depending on the TTL
Tip: If you plan to make significant DNS changes, consider lowering the TTL values for your records a few days before making the change. This can help reduce propagation time when you make the actual change. Note that BinaryLane DNS has a fixed 60-minute TTL that cannot be modified.
Managing DNS with cPanel/WHM Servers
If you're using a server with WHM/cPanel, there are some important considerations regarding nameservers and DNS management:
Option 1: Use Your Server's Nameservers
You can configure your server to act as a nameserver for your domains. With this option:
- DNS records are managed through the WHM/cPanel interface
- Your domain's nameservers would be set to your server's nameservers
- You're responsible for ensuring your server's nameserver software is properly configured and maintained
Option 2: Use BinaryLane's Nameservers
You can use BinaryLane's nameservers while still having your site hosted on your WHM/cPanel server. With this option:
- Set your domain's nameservers to BinaryLane's nameservers at your domain registrar
- DNS records must be configured in BinaryLane's mPanel (not in WHM/cPanel)
- Point your domain to your server's IP address using A records in mPanel
Warning: A common mistake is configuring DNS records in WHM/cPanel while using BinaryLane's nameservers. These configurations won't work together because: 1. Records set in WHM/cPanel only work when using your server's nameservers 2. When using BinaryLane's nameservers, you must manage ALL DNS records in mPanel Changes made in WHM/cPanel will NOT automatically synchronize with BinaryLane's nameservers.
Recommended Approach for BinaryLane Customers
For most BinaryLane customers, we recommend the following approach:
For Small Websites and Personal Projects
- Use BinaryLane's nameservers or your domain registrar's nameservers
- This provides a straightforward setup with sufficient reliability for typical websites
- If you registered your domain through BinaryLane, our nameservers are automatically configured
For Business or Enterprise Websites
- Consider using a dedicated DNS provider like Cloudflare (which offers a free tier) or Amazon Route 53
- Benefits include improved performance, additional security, and advanced features
- If DNSSEC is required, use a provider that supports it
For cPanel/WHM Customers
- Simple approach: Use BinaryLane's nameservers and manage DNS records in mPanel
- Advanced approach: If you need WHM/cPanel DNS management features, use your server's nameservers instead
How to Change Your Domain's Nameservers
If you decide to change your nameservers, the process typically involves:
- Log in to your domain registrar's account
- Locate the domain management or DNS settings section
- Find the nameserver settings (sometimes called "DNS servers" or similar)
- Enter the new nameservers provided by your chosen DNS provider
- Save your changes
If you registered your domain through BinaryLane and want to use BinaryLane's nameservers, they are already set for you by default.
Warning: Nameserver changes can take 24-48 hours to fully propagate across the internet. During this time, some users may be directed to your old DNS settings while others see your new settings. Plan accordingly and avoid making critical DNS changes during high-traffic periods.
Conclusion
Choosing the right nameservers for your domain is an important decision that affects the reliability, performance, and security of your online presence. For most users, leveraging third-party DNS services offers the best balance of reliability, features, and cost-effectiveness.
Self-hosting nameservers should only be considered by organisations with specific requirements and the technical resources to properly maintain this critical infrastructure. Remember that DNS is the foundation of your online presence—if your nameservers fail, none of your online services will be accessible by domain name.
If you have specific questions about configuring DNS for your BinaryLane services, our support team is available to help guide you through the process and recommend the best solution for your particular needs.