• Industry Solutions
    • Managed Service Providers
    • Enterprise Solutions
    • Developers & Startups
    • Healthcare
    • Trading and Financial
      • Chicago Managed Trading Servers
      • Trading and Financial Colocation: Chicago & New Jersey
    • IBM AS/400 and iSeries Users
  • Support
    • Register
    • View Tickets
    • Submit a Ticket
    • Knowledgebase
    • News
  • Steadfast Blog
  • Steadfast Podcasts
  • Contact Us
Home
  • Call Us
  • Call | 888.281.9449
  • Login
  • Search

This form logs you into your management portal account. To access your help desk account, click here and use the form to the right of the news.

  • Cloud Hosting
    • Cloud Hosting
    • Private Cloud
    • Hybrid Cloud
    • Public Cloud
    • Cloud Storage
      • Secure File Share
      • Wasabi Cloud Storage
    • Virtual Data Center Platform
  • Managed Hosting
    • Bare Metal Dedicated Servers
      • Deep Learning GPU Dedicated Servers
      • Linux Dedicated Servers
      • Windows Dedicated Servers
    • Virtual Private Servers
    • Data Center Colocation
      • Managed Colocation
      • Chicago: 350 E Cermak
      • Chicago: 725 S Wells
      • Edison, New Jersey
    • Security & Compliance
      • Managed Firewall
      • SSL VPN
      • DDoS Protection
      • Email Security
  • Backup & Disaster Recovery
    • Backup
    • Disaster Recovery
    • Veeam Backup & Replication
    • Veeam Cloud Connect
    • Wasabi Cloud Storage
  • Why Steadfast
    • Why Steadfast?
    • About Steadfast
      • Our History
      • News and Press
    • Data Centers & Network
      • Our Data Centers
      • Our Network
      • Network Test
      • Peering Policy
    • Customer Stories
    • Service Level Agreement
  • Industry Solutions
    • Managed Service Providers
    • Enterprise Solutions
    • Developers & Startups
    • Healthcare
    • Trading and Financial
      • Chicago Managed Trading Servers
      • Trading and Financial Colocation: Chicago & New Jersey
    • IBM AS/400 and iSeries Users
  • Support
    • Register
    • View Tickets
    • Submit a Ticket
    • Knowledgebase
    • News
  • Steadfast Blog
  • Steadfast Podcasts
  • Contact Us
Close
  • Support Home
  • Register
  • Submit a Ticket
  • Knowledgebase
  • News
 Login Subscribe

Log into the help desk to manage support tickets.


Lost password

Subscribe to general maintenance announcements and advisories.



 
 Knowledgebase
39Steadfast Cloud Platform 3Full Management 38Dedicated Servers & Colocation 4Control Panels 19Other
Search
Knowledgebase: Other
Creating a nameserver using eNom
Posted by - NA -, Last modified by Kevin Stange on 17 June 2016 02:39 PM

These instructions explain how to define a nameserver that you will host on your own server if your domain is registered through eNom. This document is not an endorsement of eNom's services, it merely provides instructions to a frequently asked question.

You must be running nameserver software on your server in order for this procedure to be useful. If you have a control panel on your server, this should already be the case.

For this example, we will use the following nameserver:

ns1.example.com (10.0.0.1)

  1. Log into eNom through the domain management interface.
  2. Hover over the "Domains" menu along the top of the page, then move down to "Advanced Tools" and click "Register a Name Server."
  3. Locate the "Register a NameServer Name" section and enter "ns1.example.com" in the box for "NameServer" and "10.0.0.1" in the "IP Address" box.
  4. Click the "submit" button to create the nameserver record. If you need to create more nameservers, simply repeat these steps for each nameserver.

If you want this domain to use your newly created nameservers, simply return to the "My Domains" page, click on the domain and set ns1.example.com (and any additional nameservers) as the nameserver your domain will use under the "DNS Server" section.

You should allow 24-48 hours for propagation of these changes on the Internet, however most of the time everything should begin working within 4 hours.

(244 vote(s))
Helpful
Not helpful

Comments (1)
John Middlemas
11 June 2007 11:14 PM
In step 3 the IP address should not be 10.0.0.1 since it is just an example but should be an IP that you have available on your own server.

I consent to allow Steadfast to process my data and agree to the Acceptable Use and Privacy Policies

  • 312.602.2689
  • ColoHouse Sales
  • Facebook
  • Twitter
  • YouTube
  • LinkedIn

Services

  • Cloud Hosting
  • Managed Hosting
  • Backup & Disaster Recovery

Solutions By Industry

  • Enterprise Solutions
  • Trading & Financial
  • Healthcare
  • Developers & Startups
© 2023 Steadfast
  • Log In
  • Site Map
  • Legal Info & Privacy Policy