View Single Post
  #4  
Old 7th March 2009, 15:39
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,711
Thanks: 1,899
Thanked 2,702 Times in 2,545 Posts
Default

Quote:
Originally Posted by rrhode View Post
I want IP address 192.168.0.100 to be my primary address and the only domain I want to point at this address is mydomain.com. Would I then set ns1.mydomain.com to this same .100 IP address?
ns1.mydomain.com is independent from mydomain.com, so it can point to any IP address. But if your nameserver lsitens on .100, then point ns1 to that IP.

If you want to host the mydomsin.com zone on ns1.mydomain.com, you need a glue record: http://en.wikipedia.org/wiki/Domain_...d_glue_records

BTW, you must use public IP addresses for your records, or nobody from outside your LAN will be able to access your servers.

Quote:
Originally Posted by rrhode View Post
Would I set ns2.mydomain.com to a unique address, the 101?

I would want any other domains to point to a separate IP address completely so they would all share an IP such as 192.168.0.102 or 101 but should 101 be reserved completely for ns2.mydomain.com?

Or is it possible to point them to the same as the IP as ns2 subdomain so I can free up one IP address if needed?
Normally you should set up ns2 on a completely different server so that it can take over if ns1 fails. In your case, it doesn'T make much sense to have ns2 because it's on the same server as ns1, and if ns1 is down, ns2 is down as well.
But as registrars need two nameservers, you can create a record for ns2 anyway. But it is possible that some registrars won't accept it because it's using the same IP as ns1 (if you use .100 for ns2 as well) or in the same subnet.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote