Help addressing different domains and/or zones

[Barry Margolin]

In article <CD4FCCD776FDD211986F00A0C9A70947269132 at sbnt4.ogse.com>,
Anthony O. Brinson <abrinson at ogse.com> wrote:
>A follow-up question, then.  I am trying to do this exact thing, and I 
>was curious about the SOA.  
>In the main domain you would obviously put the following as the first 
>line.
>
>@       IN      SOA     ns.dom1.com. hostmaster.dom1.com.  (
>
>My question is for the second domain would you put 
>
>@       IN      SOA     ns.dom2.com. hostmaster.dom2.com.  (
>
>or would you list the actual name of the DNS server as below
>
>@       IN      SOA     ns.dom1.com. hostmaster.dom1.com.  (
>
>The book (in my opinion) is not completely clear on this.

In general, you should put the real hostname of the primary nameserver.
But it usually doesn't matter, since the hostname in the SOA record isn't
used for much.  The only thing it's currently used for is determining where
to send dynamic DNS updates; if you're not using DDNS, don't worry about
it.

>I am having troubles using nslookup on a new domain.  carissadeason.com
>
>When I run nslookup from an outside nameserver, it checks looks for
>www.carissadeason.com.ogse.com instead of www.carissadeason.com.
>
>I am assuming I have done something wrong in my db file.

The problem is that the root servers list ogutility.ogse.com and
ns2.ogse.com as the nameservers, but you have ogutility entered as a CNAME
record in your DNS rather than an A record.  As a result, caching servers
are trying to use ns2 as the nameserver, and it seems to be down.  Change
ogutility to an A record -- NS records are always supposed to point to A
records.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.