nameservers help

A

andyfitz

Verified User
Joined
Aug 17, 2008
Messages
14
Could someone please help me set up the nameservers in my server.
I have a server with ips **.***.**.101 to 105.
101 is the server.
I've read a few tutorials but nothing seems to work...
There are nameservers on there already that don't work, so i'd like to start from scratch.
Any help at all would be great as i'm pulling my hair out over this !!!
Andyfitz
 
It's pretty straight forward.

Lets say you want .101 and .102 as ns1 and ns2 respectively.

Go to Reseller->Nameservers

Assuming you already added the domain, select the domain from the drop down. Click the "create" button.

Now go to your domain registrar and create nameservers. Use 101 and 102, wait a few hours (varies) and it should start resolving.
 
Hi GXX, thanks for your help. I've done as you described but the domain registrars won't let you put the ip's in, they want the nameservers.
 
You are editing nameservers, which is why it is asking for non-ip.

You want to create nameservers based on the domain.
 
Hi, Thanks again.
O.k. I'd changed the nameservers at the domain hosts to the nameservers on my server.These were flagging up as " nameservers not registered "
So after your advice i've been back to the domain hosts, changed the nameservers to the original supplied. ( this is where i thought you had to do the change )
Anyway... in the control panel i clicked on advanced dns settings and there it asked for the ip address of your domain and email.
Done this and just waiting to see if it resolves...
Speak to you later, thanks...
 
You have to create nameserver records at the registrar. Nothing you do on your server can change that. It has to be done at the registrar where you registered the domain you want the nameservers to be based on. How you do that depends on who the registrar is.
 
Thanks Floyd,
o.k. Let me get my thick skull around this !
Should i forget about creating nameservers on my server ( what's the purpose of this anyway ? )

Should i simply use the nameservers that are supplied when you buy a domain name and put them as the nameservers when i create a domain on my server ?
 
Should i forget about creating nameservers on my server
Click to expand...

No. You have to do it on your server too if you are using nameservers based on one of your domains.


Should i simply use the nameservers that are supplied when you buy a domain name and put them as the nameservers when i create a domain on my server ?
Click to expand...

You have to use the nameservers that are going to handle DNS for your domain.

Maybe this will help
 
Andyfitz and others who sometimes get confused on this:

Look at it this way.

First you have to set up your nameservers on your own server(s). Once they work you have to register them with the registar where you registered the domain your nameserver is based on (see floyd's post, #6, above).

Why? Because if your nameservers' IP#s are only resolved at your nameserver then how would any server on the 'net know where to look to find it's IP#. Your nameserver's IP# must be registered at the TLD's root servers (in the case of .com/.net in the gtld servers).

Floyd, thanks for that link (your post above #8)!

Jeff
 
andyfitz said:
Hi, Thanks again.
O.k. I'd changed the nameservers at the domain hosts to the nameservers on my server.These were flagging up as " nameservers not registered "
So after your advice i've been back to the domain hosts, changed the nameservers to the original supplied. ( this is where i thought you had to do the change )
Anyway... in the control panel i clicked on advanced dns settings and there it asked for the ip address of your domain and email.
Done this and just waiting to see if it resolves...
Speak to you later, thanks...
Click to expand...

Do not use you custom nameservers yet until they start resolving. Otherwise, your registrar will complain about them not being registered yet.

All you need to do like I said, is to create nameservers based on your domain (at your registrar) with two IPs of your choosing. Once they resolve, you can then start using them with your domain(s). For now, you can leave the domain with their default nameservers given by your registrar.
 
Many registrars of country TLDs require working nameservers actually resolve before they'll list them in the root servers. Why? To avoid loops through their servers, which waste resources.

To see what I mean, try a dig example.com +trace (replacing example.com with your domain name not yet in DNS) to see it loop through the top level nameservers over and over again.

Jeff
 
Back to the beginning !

O.K. i'm going to start over, as there are one or two issues that i don't understand.
First, let me say thanks for your help so far. Really the questions i'm asking should be dealt with by my server host but i don't get anywhere with them...

I believe i do understand the basics of the nameservers,setting them up on your server first, letting them resolve etc. I've done this for 72 hours with no joy.

I think it may be down to how things were set up on my server,
i'll describe next post......
 
At first my server was set up with direct admin.
Because i didn't have a clue where to start, i asked my server host to set up a domain for me, as i needed it asap.
This took about 3 weeks of nagging before it happened.

My server has ip's **.***.**.101 to 105.
looking at the ip setup 101 is the server 102 has the ***.com domain on it.
the rest are free.
101 was setup with ****.nameresolution.net on it ( i presume this is because i need 2 nameservers ?)

102 was setup with ****.my.com on it

I was given NS5.****.nameresolution.net and NS6.****.nameresolution.net,
as the nameservers for my.com

These didn't work, so i joined zonedit, used their nameservers and pointed the domain straight at **.***.**.102 Eureka ! my .com works.

Now after about a year i'm getting a bit more to grips with direct admin, and i'd like to use my server more. I don't want to use zonedit if i can do the job on my own server, i'd like to do it in house.

Sorry for this long rant, but if anyone can help getting this thick brain around what's going wrong and how to resolve this .....

Thanks,
Andyfitz
 
It would help if you gave us real domains and ips and nameserver records to work with.
 
Thanks Floyd. Being a relative newbie i didn't want to get hacked and god knows what else by revealing too much !
Let me know what you need and what's safe to put online,
Thanks,
andyfitz
 
andyfitz said:
You get out the wrong side of bed ?
Click to expand...

No I didn't. I am not sure what you mean by that. You asked:
Let me know what you need and what's safe to put online,
Click to expand...

I gave you the answer. Don't you want your web site and dns to be published? I mean that is the whole idea of having a web site. You want to get it out there so people will come to it.

You will find that if you want to get help with a domain or dns we cannot really help unless we know what the domain is and what the ip address is supposed to be.

But yet even after reading the link above you are still unwilling to help us help you. I so guess we are done here.
 
We seem to have had a misunderstanding here Floyd,
i do want help but just didn't want to make a huge mistake thru my ignorance.
I've read the article you linked to, i was ignorant of these facts. If you are still willing to advise, here are the settings :

IP's

64.191.39.101 server 0 ns1.pippalvinn.com 255.255.255.240
64.191.39.102 owned admin pippalvinn ns2.pippalvinn.com 255.255.255.111



DNS for pplv.nameresolution.net

ftp A 64.191.39.101
localhost A 127.0.0.1
mail A 64.191.39.101
pop A 64.191.39.101
pplv.nameresolution.net. A 64.191.39.101
smtp A 64.191.39.101
www A 64.191.39.101
pplv.nameresolution.net. NS pippalvinn.com.
mail MX 10
pplv.nameresolution.net. TXT "v=spf1 a mx ip4:64.191.39.101 ?all"



DNS for pippalvinn.com

ftp A 64.191.39.102
localhost A 127.0.0.1
mail A 64.191.39.102
ns1.pippalvinn.com. A 64.191.39.101
ns1.pippalvinn.com. A 64.191.39.102
pippalvinn.com. A 64.191.39.102
pop A 64.191.39.102
smtp A 64.191.39.102
www A 64.191.39.102
pippalvinn.com. NS ns1.pippalvinn.com.
pippalvinn.com. NS ns2.pippalvinn.com.
mail MX 10
pippalvinn.com. TXT "v=spf1 a mx ip4:64.191.39.101 ?all"


If you need anything else do let me know.
If you decline to help i respect your decision.
Andyfitz
 
You must log in or register to reply here.
Back
Top