Results 1 to 7 of 7
Thread: WHM nameserver problems
-
11-17-2013, 04:10 PM #1Junior Guru Wannabe
- Join Date
- Apr 2013
- Posts
- 74
WHM nameserver problems
Hi all, Recently started using WHM after 6 months of using Plesk (no live site yet as taking my time learning how to manage my cloud vps). Apologies if this is something simple as i have been unwell for several weeks and a rather bad brain fog.
In Plesk I created a DNS zone for myself then assigned the nameservers. In WHM you have to list the nameservers in the initial setup. Both nameservers have been given a zone, hostname has also been given a zone. I have been unable to resolve the nameservers with my domain registrar's glue records (I am using com for hostname and website and net for the nameservers. I have assigned the relevant IPs).
Do I need to set up all websites in the ns1 zone? I want my web hosting website on its own dedicated ip eg
.223 host
.224 nameserver1
.225 dedi ip for website
.225 nameserver2
.226 shared ip for web hosting customers
.227 unallocated
.228 unallocated
.229 unallocated
Thanks for any advice or links to information.
Earthblaze
-
11-17-2013, 04:24 PM #2Web Hosting Master
- Join Date
- Sep 2013
- Location
- Canada
- Posts
- 656
If you use bind, try to resolv your hostname from console. If it works then your only issue is to properly register your nameserver with your registrar.
By default WHM does everything for you, just assign 2 or more nameservers, and when you had a domain it will automatically create proper dns zones.
I think your issue right now is only with your registrar.Hostabulous 🔗 cPanel (Cloudlinux) & Plesk (Windows DC 2016) Hosting 🔗 R1Soft CDP backups
No Gimmicks 🍁 Proudly Canadian
-
11-17-2013, 04:36 PM #3Junior Guru Wannabe
- Join Date
- Apr 2013
- Posts
- 90
wait for the propagation and then ask your domain registrar to resolve glue record issue or to create child name servers for you.
-
11-18-2013, 02:46 PM #4Junior Guru Wannabe
- Join Date
- Apr 2013
- Posts
- 74
Hi, hostname resolves and so does dnsdomainname. I have raised a support ticket. Thanks guys.
-
11-20-2013, 09:38 PM #5Newbie
- Join Date
- Nov 2013
- Posts
- 5
make sure that the configuration in your server is correct with the below command.
dig @server-IP domain-name
If this is correct you need to correct the glue record.
-
11-20-2013, 09:57 PM #6Web Hosting Master
- Join Date
- Jul 2005
- Location
- New Jersey, US
- Posts
- 1,597
After you create the domain in WHM, it will automatically setup the dns zone and NS records for it. You don't have to do anything manually, assuming the server and nameservers were configured correctly when the server was first setup. You can run a test at www.intodns.com for your domain to check it.
PlatinumServerManagement (also known as PSM)
The OLDEST and LARGEST and MOST TRUSTED server management provider in the USA, with 15+ employees and growing!
Providing quality support for OVER 21 years! Currently supporting over 3,000+ servers monthly!
www.PlatinumServerManagement.com Proud member of the NJ BBB & Chamber of Commerce & Authorized cPanel Partner.
-
11-20-2013, 10:31 PM #7Junior Guru Wannabe
- Join Date
- Apr 2013
- Posts
- 74
Thanks guys I will try this today. I received a support request from OVH which is quite a complicated. I first have to change to their nameservers. I have done this but the dot net domain is trapped on a spooi. Why do they make is so complicated?
Regards,
Philip
Similar Threads
-
Nameserver problems...
By skoobi2 in forum Dedicated ServerReplies: 4Last Post: 09-22-2010, 01:06 PM -
Nameserver problems.
By Cyberkiller in forum Hosting Security and TechnologyReplies: 2Last Post: 11-22-2006, 08:29 PM -
problems with site copy in whm (cpanel) and changing nameserver ip's
By -Ley- in forum Hosting Security and TechnologyReplies: 2Last Post: 12-08-2004, 05:48 PM -
nameserver problems...
By seattlite in forum Web HostingReplies: 7Last Post: 08-24-2001, 04:51 PM