If you are new to domains and looking to buy, sell and learn about domains then you have come to the right place. DNForum is the largest domain name community on the internet and continues to grow every day. There are over 105,000 domainers on DNForum doing everything from buying domains, selling domains, learning about domains and discussing domains. Take a minute and Register.
Register Today on DNForum IT'S FREE!I have a dedicated server that I have been using a domain of mine as a dns for over a year. The domain I use is currently at enom and it is a .net.
I just recently acquired a .org domain, which is at a different registrar. When I tried to set my usual dns as the nameservers, I get this error:
"Unable to update nameservers: ns1.domain.net not a registered NS host in the .org Registry (480)
This means that ns1.domain.net has not been registered as a
nameserver host at the .org registry. The administrator of
ns1.domain.net will need to create a nameserver host record in the .org registry via their domain registrar."
Anybody know hat are they talking about, and how to fix it?![]()
Where are you trying to set the new nameservers at? If they're at another registrar, that's where you set it, not at aNom.
Your .org registrar ought to be able to do this, or rather you should be able to via their control panel. Log into your .org registrar account, and find the option to create an NS entry. You'll need two. They should ideally be in the format:
NS1.YOURORG.ORG
NS2.YOURORG.ORG
The IPs for the NS should point to your own server IPs if you have two. If you only have one then use that for both entries.
fixed
Last edited by Jernet; 08-19-2007 at 11:38 AM.
it sounds like your registrar is not recognizing your name servers as being valid (resolveable)
Try emailing them about it.
Where are you trying to host the .org? On the box where the .net domain is?
Strange:
dale-hubbards-computer:~ dalehubbard$ dig -tns spamfree.org
; <<>> DiG 9.3.4 <<>> -tns spamfree.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64240
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;spamfree.org. IN NS
;; ANSWER SECTION:
spamfree.org. 3174 IN NS name3.glorb.com.
spamfree.org. 3174 IN NS amethyst.justthe.net.
spamfree.org. 3174 IN NS name1.glorb.com.
spamfree.org. 3174 IN NS name2.glorb.com.
;; Query time: 23 msec
;; server: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sun Aug 19 12:41:36 2007
;; MSG SIZE rcvd: 133
Yeah. I am trying to host it on the same box. Fortunately the old owner is leaving it on his until I can get things straightened out on my end.
*UPDATE* I finally got a response to a support ticket I sent at enom. It appears it may have been something they had to do on their end. I just entered the dns that I originaly tried to use, and the registrar accepted the changes! I think this is resolved, but I will believe it when I see it propogate with my page on it.....![]()
Last edited by Jernet; 08-19-2007 at 11:38 AM.
dale-hubbards-computer:~ dalehubbard$ dig -tns spamfree.org
; <<>> DiG 9.3.4 <<>> -tns spamfree.org
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50987
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;spamfree.org. IN NS
;; ANSWER SECTION:
spamfree.org. 86400 IN NS ns1.jer.net.
spamfree.org. 86400 IN NS ns2.jer.net.
;; Query time: 365 msec
;; server: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sun Aug 19 14:54:24 2007
;; MSG SIZE rcvd: 73
dale-hubbards-computer:~ dalehubbard$ ping jer.net
PING jer.net (67.18.52.95): 56 data bytes
64 bytes from 67.18.52.95: icmp_seq=0 ttl=49 time=123.260 ms
64 bytes from 67.18.52.95: icmp_seq=1 ttl=49 time=124.168 ms
^C
--- jer.net ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 123.260/123.714/124.168/0.454 ms
dale-hubbards-computer:~ dalehubbard$ ping strausser.net
PING strausser.net (69.93.84.186): 56 data bytes
64 bytes from 69.93.84.186: icmp_seq=0 ttl=50 time=123.168 ms
64 bytes from 69.93.84.186: icmp_seq=1 ttl=49 time=121.849 ms
DNS has updated but jer.net is on a different IP range to strausser.net so you'll still have problems.
I always wondered about that azooza. I am glad you pointed that out. When I originally started renting the box, I had it set up on jer.net. I then ended up selling the domain jer.net and then had the box changed over to strausser.net. I have since then purchased my domain jer.net back, but continued to keep strausser.net as the name for the box...
Apparently the host of the box has made some of the neccesary changes, but not all of the cosmetic changes, because even when I login to whm, I still see jer.net as being the dns I should use when I create a new site. I have never had any problems setting up new Hosting accounts, so I left it go. Hopefully I don't have any problems with the .org either. This has been exhausting enough lol...
Looks like enom's fix has done the trick. It is now propogating to my servers. thanks to thos who took the time to input!
Last edited by Jernet; 08-19-2007 at 11:37 AM.
Bookmarks