Good Afternoon,

I would like to know how to go about setting up Private nameservers, such that I could put ns.anyname.com and have that run in tandem with my own nameservers.

Thanks in advance.

That depends. Do you already have a server devoted to this purpose or you are trying to set this up on your existing server or you are trying to find a host who will provide this? There are many options!

want to set this up on an existing server that already has ns.myserver.com. I want to know how to setup ns.aresellername.com on the same machine if that's possible.

Thanks again.

What OS are you running?
Do you run CPanel/WHM by any chance?
What version of bind do you have?

Are you using Web Host Manager?

Bind 8.23
Cobalt Control Panel
Redhat based cobalt OS


hope this helps, thanks again.

Originally posted by Orpheus1539
Bind 8.23
Cobalt Control Panel
Redhat based cobalt OS


hope this helps, thanks again.

That is a tuff one. To be honest with you, I don't know how to setup DNS for resellers with the Cobalt OS. If I find out I will posted here.

Is there anyone that knows how to set this up on a RaQ? :confused:

Done that before...
contact me at herps@ewsnl.com and I'll see what I can do for you...

Would you mind sharing your knowledge with the board?

Sure,

contact me first,
let me have a look at it,
and I'll post my report here,
that ok? :)

Sorry Eagle, I am not about to give you full access to my machine. Does anyone Else have any suggestions?

Regards.

Fine, suit ya self...
Do you really think I'm gonna screw up your RaQ and damage my goodwill? Think again...
That's not my style...
Just trying to help
ah well....

Why all this fuzz over something _so_ simple?

Creating extra nameservers is _easy_ on the RaQ. Simply create a site using the IP address you want the nameserver on - and it will work.

(if you want to do ACLs based on the IP-address, I'll recommend upgrading to Bind9 and use views)

--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@mermaidconsulting.dk,
http://www.mermaidconsulting.com/

Duh! jks is absolutely right. I never though of that. Just simply setup a couple of virtual sites, have each site share each one of the IPs for each one of your existing DNS, call the sites NS1.DOMAIN.COM, NS2.DOMAIN.COM, and then simply create an A record and perhaps a PTR record to each, you are done! ;)

Originally posted by bert
Duh! jks is absolutely right. I never though of that. Just simply setup a couple of virtual sites, have each site share each one of the IPs for each one of your existing DNS, call the sites NS1.DOMAIN.COM, NS2.DOMAIN.COM, and then simply create an A record and perhaps a PTR record to each, you are done! ;)

Sorry bert, but you misunderstood it.

There is no point in having them share IPs with your existing nameservers -- that will give you nothing you didn't already have.

The point is, that by creating a site with a new ip-address, you'll get another virtual interface. This means that bind (dns server) will start listening on this new ip-address.

I.e. for each IP-address that has a site associated in the Cobalt GUI - you'll also have a DNS server.

If you wanted them on the same IP address as your existing nameservers - you wouldn't have to do anything at all - it would work instantly. Just add an A record for ns1.reseller.com that points to the address of your currenct nameserver. The problem with this is, that systems like Network Solutions only allow one nameserver per IP address.

Conclusion:

Each additional nameserver require an IP address of it's own.

You need to have at least one site on the IP address to activate it.

--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@mermaidconsulting.dk,
http://www.mermaidconsulting.com/

Isn't this what I said? You have to then create virtual site to be able to have an IP associated with the new host name, then create the A record, and maybe a PTR record to prevent possible email problems down the road. Isn't this correct?

Originally posted by bert
Isn't this what I said?

Not quite. You wrote before:

"have each site share each one of the IPs for each one of your existing DNS"

This is what I was opposing. You should not let them share IPs with your existing nameservers.

You have to then create virtual site to be able to have an IP associated with the new host name, then create the A record, and maybe a PTR record to prevent possible email problems down the road. Isn't this correct?

Again, not quite. There is no need to create a virtual site named "ns1.reseller.com" as long as you have a site associated with the ip-address.

I.e. there is no "name relationship" when talking DNS.

BTW: Remember to just have exactly one PTR record for any IP-address.

--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@mermaidconsulting.dk,
http://www.mermaidconsulting.com/
http://www.raqsupport.net/

So, if you don't create a virtual site, how else can you associate a host name with an IP address?

How can you register a DNS host with your registrar if that host name cannot be pinged?

Sorry for the confusion, but don't quite understand it well. Thanks! ;)

Originally posted by bert
So, if you don't create a virtual site, how else can you associate a host name with an IP address?

How can you register a DNS host with your registrar if that host name cannot be pinged?

Sorry for the confusion, but don't quite understand it well. Thanks! ;)

You seem to have one misunderstanding, that makes the rest hard to understand.

There is no such thing as pinging a hostname -- you always ping an IP-address. If you type:

ping www.hostname.com

Then www.hostname.com is resolved into an IP-address before the ping program tries to ping it.

This means that you can have a site named www.toys-r-us.com on 123.123.123.123 - and then if you setup an A record for ns1.reseller.com to point to 123.123.123.123 then you can go:

ping ns1.reseller.com

and it will still work -- despite the fact that you didn't create a site named ns1.reseller.com

[DISCLAIMER: This explanation is an explanation. Exact technical correctness was not the goal, as that would make it harder to understand]

--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@mermaidconsulting.dk,
http://www.mermaidconsulting.com/

JKS - THANK YOU. I was really beginning to think that it just couldn't be done. I never thought the answer would be so simple, but then again, most things are.


Regards.

I understand the concept completely. I just didn't look at it that way. I guess you can then create a PTR record and the reverse will work as well.

Originally posted by bert
I understand the concept completely. I just didn't look at it that way. I guess you can then create a PTR record and the reverse will work as well.

Yes, but again: Only one PTR record per IP-address.


--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@mermaidconsulting.dk,
http://www.mermaidconsulting.com/

Originally posted by jks


Yes, but again: Only one PTR record per IP-address.


--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@mermaidconsulting.dk,
http://www.mermaidconsulting.com/

You got it. :D

I run a raq4 with DNS.

If I had virtualsite1.com
I can create 2 virtual DNS for that domain as long as I have 2 extra IP addresses for the nameservers.

I would have to create 2 virtual sites ns1 and ns2 and point them to the 2 new IPs.

I think that is all to it. I do believe that it is explained in the raq manual. http://www.cobalt.com/support/

Any corrections welcome.