 |  |
At 6:01 PM -0600 1/17/2000, Matthew Seifert wrote:
Re: Fractional Class C Reverse Domain AND Authoritativ
From: Men & Mice Support
Date: Tuesday, January 18, 2000
Time: 4:43:00 am
>on 1/17/00 5:22 PM, Mia's Virtual Post Office at list@mia.net wrote:
>
>>> We run QuickDNS Pro on our fractional class C, managing about 18 registered
>>> domains, IP ranges 207.170.22.64 through 207.170.22.127 (Subnet mask
>>> 255.255.255.192). Our ISP runs BIND DNS, I believe.
>>
>> First, I am a bit confused.. I assume this is a Fractional T1 and a /26
>> we are talking about?
>
>I meant "Part of a class C". It's a Full T1, and by what I read recently in
>a Cisco book, it would be a /26 we have, I believe.
>
>>> The second issue has to do with delegation of authoritative nameservers.
>>> Right now I'm trying to avoid a lame delegation, but it seems that under the
>>> current set-up, anytime we register a new domain, our ISP has to be told
>>> directly if their DNS server will act as a secondary to ours. Is there a
>>> way to automate this process, so that anytime we add a primary domain to
>>> QuickDNS, that their nameserver will receive it and become authoritative?
>>>
>> If you could build the zone 64.22.170.207.in-addr.arpa (the 64 refers to
>> your network number) with your reverse lookups in it. Once this is done,
>> your ISP should set up the name server on his end to transfer that zone
>> from you. Your zone should look something like this:
>>
>> 64.22.170.207.in-addr.arpa. NS youdnsserver.you.com.
>> 64.22.170.207.in-addr.arpa. NS yourISPsdnsserver.them.com.
>> 64.64.22.170.207.in-addr.arpa. IN PTR device1.you.com.
>> 65.64.22.170.207.in-addr.arpa. IN PTR device2.you.com.
>> ..
>> ..
>> ..
>> ..
>> 127.64.22.170.207.in-addr.arpa. IN PTR device64.you.com.
>
>With the second question I was actually referring to delegation of forward
>domains, not reverse like in Question 1, but your comments bring up
>something interesting. Mr. Rent-A-Tech also told me that my reverse domain
>configuration should be 22.170.207.in-addr.arpa, and not with the "64" in
>front of it. I know that 64 is my network number, so was he wrong? I'm a
>little unclear as to how this should be correctly specified. I read over
>the RFC link you sent me about what my ISP should do and it makes perfect
>sense, but how should I set my QuickDNS? Should the reverse domain be
>called: 64.22.170.207.in-addr.arpa, or 64/26.22.170.207.in-addr.arpa, or
>what?
It should be whatever your ISP decides it should be.
If they decide to use the simplest and most comprehensible approach, they will do exactly what Jer (Mia's Virtual Post Office) said, 64.22.170.207.in-addr.arpa.
If they follow the example solution in the RFC to the letter, they'll use 64/26.22.170.207.in-addr.arpa.
Another possibility would be portalmedia.22.170.207.in-addr.arpa.
The one thing that it should not be, under any circumstances, is 22.170.207.in-addr.arpa. This zone belongs to your ISP, and they'd have a hard time delegating it to you. Besides, you don't own all the addresses covered by it.
Don't knock Rent-A-Tech's in general, but it sounds like the one you were talking to needs some further education.
>> Am I missing something?
>
>And yes, as per my original Question 2: When we register new [forward]
>domains, we want to specify our ISPs (or other off-site) server as a
>secondary or tertiary DNS server for the domain. The problem is that unless
>we specifically the admin of that other DNS server and have the information
>put in it as a secondary nameservice, then it will not know that it's
>supposed to be authoritative. To agree with the Global Homes Webmaster, I,
>too, was under the impression that it could not be done unless I had my own
>access to it or relied upon the competence and punctuality of the
>secondary's admin to get it in there and right.
>
>The one thing that sparked this poser, was that I was told by a colleague
>that it could be achieved so that a secondary nameserver can somehow know
>that it is secondary for ALL registered domains that a particular nameserver
>is hosting as primary, and with NO admin intervention. I think I wrote this
>one in complicated language...let me illustrate:
>
>If I register a new domain foo.com with my DNS server as a primary and my
>ISP's as a secondary, I enter it into QuickDNS as a primary domain. This is
>what I want to know what's possible: Somehow, the Secondary DNS server
>knows that it is to be secondary for all domains that I register on my DNS
>server, and thus receives the information from my DNS server and
>automatically configures itself for foo.com to be authoritative as a
>secondary. The reason I ask this, is because we register new domains here
>very frequently, and it either means that (1) we call our ISP very
>frequently, or (2) what I just asked is actually possible, or (3) we look
>into putting our own secondary server off-site on someone else's rack and
>make it so that we can administer it remotely from here.
>
>I do realize that #2 may not actually be possible, and that my colleague was
>wrong, but it left me curious to ask the DNS experts about it before
>dismissing it.
This isn't possible with QuickDNS Pro 2, at least without some sort of AppleScript work on both primary and secondary servers.
A similar statement can be made with respect to BIND; some sort of Perl script work would be needed on both primary and secondary servers.
I'm not sure if this will be possible with QuickDNS Pro 3, though there has been some talk of it. However, if implemented, it will require both primary and secondary servers to be running QuickDNS Pro 3.
____________________________________________________________________
Chris Buxton cbuxton@menandmice.com
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro
Messages In This Thread:
Return to Digital Point Solutions' Home Page