Re: [PLUG] DNS/BIND9 problems

[John Von Essen <john@essenz.com>]

Back in the day when NetSol did everything there was a separate record  
specifically for nameservers, and there still is today. It used for the  
case when the IP of a nameserver changes, but not the name - the  
nameserver record gets updated, and you dont have to touch domain  
records which reference your nameserver.

When you register a new domain, and add NS entries, the registrar  
checks to see if they are pre-existing nameservers. If not, they will  
create a nameserver record for them. So just go to register.com and add  
the nameservers "ns2.passhosting.net" and "ns2.passhosting.net" to the  
passhosting.net domain record. However, ns1 and ns2 must exist prior to  
doing this. Then wait a few days, if things dont work, call  
register.com and say you are a hosting provider and having difficulties  
with registering a name server.

You really have to fool the registrar with the pri and sec NS thing.  
Just create an IP alias on your server, and run both ns1 and ns2 on the  
same machine. Here is a sample config:

$TTL 86400
passhosting.net.     IN      SOA  ns1.passhosting.net.  
noc.passhosting.net. (
                2005051106
                7200
                1800
                604800
                43200 )

; Name Servers
                        IN      NS      ns1.passhosting.net.
                        IN      NS      ns2.passhosting.net.
                        IN      MX      10  server01.passhosting.net.
ns1            IN      A       140.140.140.90
ns2            IN      A       140.140.140.91

; Hosts/Aliases
server01           		IN  	A	140.140.140.90
www				IN   	CNAME   	140.140.140.90
passhosting.net.	IN	CNAME	140.140.140.90


And..... DONT FORGET TO MAKE AN IN-ADDR.ARPA ZONE FOR REVERSE  
RESOLUTION!!! Just tell your upstream provider to delegate authority to  
your name server for the range you work off of.


-john

On Jul 9, 2005, at 4:00 PM, Chad Waters wrote:

> On 7/9/05, Chris Cera <cera@mcs.drexel.edu> wrote:
> > I'm having some trouble setting up the domain passhosting.net on
> > 209.50.161.180 for the first time.  I'm trying to have this
> > domain serve the outside world.  The domain was registered with
> > register.com, and the default domain servers were deactivated
> > weeks ago (well beyond the 48 hrs for the .net tld's TTL to
> > expire).  Do I have to register my NS's somewhere else other than
> > the domain I'm trying to run the dns on?
>
> The problem seems to be at Register.com.I don't see any name server
> entries in any of the whois lookups I performed. Once that delegation
> is straightens out, you should be fine
>
> I didn't notice any problem in your zone files during my quick glance.
>
> Actually, what is the requirement for nameservers these days? I see
> you have ns1 and ns2 pointing to the same IP. I remember about 6 years
> ago I tried to do that with a netsol registration and it kicked back
> saying I needed 2 DNSs with distinct IPs. You really should have
> reduncancy anyway. If you got a trusted friend in the same situation,
> slave up each others zones.
> _______________________________________________________________________ 
> ____
> Philadelphia Linux Users Group         --         
> http://www.phillylinux.org
> Announcements -  
> http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion  --    
> http://lists.phillylinux.org/mailman/listinfo/plug

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug