private nameservers

sneakyimp · 12-17-2010, 01:07 PM

I'm trying to set up private nameservers for a domain, mbamdev.com.

I had someone follow these instructions from the registrar, enomcentral.com:

Quote:

To register, modify or delete a nameserver (i.e., create/modify/delete glue records), please follow these steps:

* Log into your account.
* Select the menu option Domains > Advanced Tools > Register a Name Server.
* Enter the required information into the appropriate section.
* Click Submit.

You can enter IP addresses in the following format:

* IPv4 (e.g., 192.168.0.1).
* IPv6 (e.g., 2001:252:0:1:0:0:2008:9).

In order to register nameservers, the domain in question must be registered with us. The above instructions will only work for .com, .net and .org domains. To register or update nameservers using .eu or .uk domains, please see the article, How to Register or Update Nameservers Using .EU and .UK Domains. To register or update nameservers using other TLDs, please submit a support ticket with the below attributes:

* Subject: "Register/Update Nameservers"
* Question: [Include the nameserver hostnames and their respective IPs]
* Category: DNS/Nameservers
* General DNS Info

I had my guy enter:
ns1.mbamdev.com - 209.59.179.63
ns2.mbamdev.com - 209.59.179.64

However, when I try to dig any of these domains (mbamdev.com, ns1.mbamdev.com, ns2.mbamdev.com) then I get nothing.

I'm wondering if I've done something wrong...?

ddaemonunics · 12-17-2010, 03:28 PM

you must configure the dns server on
ns1.mbamdev.com - 209.59.179.63
ns2.mbamdev.com - 209.59.179.64

I mean install bind, configure zone host file etc..
use whois to see if the domain has nameservers set up then dig @ns1.mbamdev.com mbamdev.com to see if the dns servers respond correctly

MensaWater · 12-17-2010, 03:33 PM

The name servers for mbamdev.com are not the ones you show - they are:
ns1.boomcycle.com and ns2.boomcycle.com per the below dig

Code:

dig -t ns mbamdev.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> -t ns mbamdev.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45576
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;mbamdev.com.                   IN      NS

;; ANSWER SECTION:
mbamdev.com.            172755  IN      NS      ns1.boomcycle.com.
mbamdev.com.            172755  IN      NS      ns2.boomcycle.com.

;; ADDITIONAL SECTION:
ns1.boomcycle.com.      172755  IN      A       209.59.178.232
ns2.boomcycle.com.      172755  IN      A       209.59.178.233

;; Query time: 6 msec
;; SERVER: 10.0.4.108#53(10.0.4.108)
;; WHEN: Fri Dec 17 16:29:42 2010
;; MSG SIZE  rcvd: 107

Note: If you previously used the boomcycle.com DNS servers and recently made this change it may be it is just taking a while to propagate but I doubt it. As I've never gone to boomcycle.com or mbamdev.com before today it doesn't seem likely it is cached anywhere along the path I'd get to it.

sneakyimp · 12-17-2010, 04:14 PM

Quote:

Originally Posted by ddaemonunics

you must configure the dns server on
ns1.mbamdev.com - 209.59.179.63
ns2.mbamdev.com - 209.59.179.64

I mean install bind, configure zone host file etc..
use whois to see if the domain has nameservers set up then dig @ns1.mbamdev.com mbamdev.com to see if the dns servers respond correctly

The target machine (to which both of those IPs are assigned) has Webhost Manager / CPanel installed. If you ask it using an IP address, it coughs up the correct DNS info:

Code:

[root@nameserver ~]# dig mbamdev.com @209.59.179.63

; <<>> DiG 9.3.3rc2 <<>> mbamdev.com @209.59.179.63
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9337
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;mbamdev.com.                   IN      A

;; ANSWER SECTION:
mbamdev.com.            14400   IN      A       209.59.179.63

;; AUTHORITY SECTION:
mbamdev.com.            86400   IN      NS      ns1.mbamdev.com.
mbamdev.com.            86400   IN      NS      ns2.mbamdev.com.

;; ADDITIONAL SECTION:
ns1.mbamdev.com.        14400   IN      A       209.59.179.63
ns2.mbamdev.com.        14400   IN      A       209.59.179.64

;; Query time: 41 msec
;; SERVER: 209.59.179.63#53(209.59.179.63)
;; WHEN: Fri Dec 17 17:12:35 2010
;; MSG SIZE  rcvd: 113

The problem is that you cannnot refer to the machine by any named domain using mbamdev.com because the world does not yet know where to find this domain and this domain's nameservers are ns1.mbamdev.com and ns2.mbamdev.com. It's a chicken-egg thing. People trying to find mbamdev.com look for ns1.mbamdev.com but they can't find it -- and vice versa.

sneakyimp · 12-17-2010, 04:16 PM

Quote:

Originally Posted by MensaWater

The name servers for mbamdev.com are not the ones you show - they are:
ns1.boomcycle.com and ns2.boomcycle.com per the below dig

You are correct that this domain had been moved. We changed the registration record about 5-7 hours ago as of right this moment.