Search Again:

Re: Lame Delegation

From: Men & Mice Support
Date: Wednesday, June 9, 1999
Time: 5:58:00 am

>>>1)We are registered with internic as ns1.valueport.com. However there is
>>>no such record in our dns. There is only ns.valueport.com. So when I go
>>>to do ns2.valueport.com, how will I do that? How do I name my secondary
>>>domain name properly?
>>
>>In the best of all worlds, you'd fix this. Aside from that, I'm not sure
>>what you're asking.
>
>so what would we do, remove the cname from our primaries records and change
>the Internic address to just like ns.valueport.com? What about our
>secondary server, what would we make it?
>
>ns2.valueport.com
>209.209.9.60

The simplest way to fix the discrepancy between Internic and your data is
to change your data to match theirs.
valueport.com. NS ns1.valueport.com.
valueport.com. NS ns.infoasis.com.

Of course, since you're planning to start doing secondary service yourself,
you'll also want to add this:
valueport.com. NS ns2.valueport.com.

You also need address records for your name servers (not infoasis', though):
ns1.valueport.com. A 209.209.9.59
ns2.valueport.com. A 209.209.9.60

I see in your domain data (which I pulled from your server) that you have
the following CNAME records:
mail.valueport.com. CNAME valueport.com.
ns1.valueport.com. CNAME valueport.com.
www.valueport.com. CNAME valueport.com.

The first of these 2 are going to cause problems (www is fine). You should
replace them with A records. Furthermore, you have the following record:
valueport.com. MX 20 mail2.valueport.com.

But you have no A record for mail2.valueport.com. This is an error.

><The secondary doesn't need to know the name of the primary, just the
>address. So it doesn't care what name you give the primary in the zone
>file. It will pull a copy of the zone file and use it as is.>
>
>So how hard it is to secondary anyhow? Is it like you just set up one
>record and that's it? I have ten virtual domains. Do I need their
>information all on my secondary as well, or what?

Yes, you need a record for each domain in the Secondary Domains file on the
secondary server.

><The name you give your secondary doesn't have to be ns2.valueport.com; it
>can be anything.valueport.com. The name is irrelevant, so long as it is (a)
>legal according to the host naming rules, and (b) unique within your domain.>
>
>Where does my secondaries name go in my secondaries dns? I copied over all
>the records and data from the primary and put it in a folder so that it all
>opens when I open DNS pro. Did I not need to do that?

No, you didn't need to put the domain files on the secondary. You just need
to set up the secondary data file. This involves setting up one record per
domain. For instance, in addition to valueport.com you also have
steinhauerphotography.com. So you'd put these two records in the Secondary
Data file on your secondary server:
valueport.com. valueport 209.209.9.59
steinhauerphotography.com. steinhauer 209.209.9.59

><Your example above is absolutely correct. This is what you'd put in the
>Secondary Data window on your secondary server.
>
>Most likely, you won't want to put anything in the Secondary Data window on
>the primary server. You'd only do that if your primary server
>(ns.valueport.com) was acting as secondary for another domain.>
>
>so let me get this right...all I need to do to secondary somebody is to
>type in that information and it will secondary all the virtual hosts as
>well?

You need the information for each individual domain. Also, most DNS servers
are set to restrict zone transfers to just those servers that are
authorized to act as secondary servers for the domain. In other words,
other organizations' servers wouldn't let your server get the zone data
unless they wanted you to.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com http://www.menandmice.com



Messages In This Thread:



Return to Digital Point Solutions' Home Page