QDNS 3.53 crash

Re: QDNS 3.53 crash

From:

Date:

Time:

>> Another question I have is: Why do I get lame delegations from the root
>> servers?
>
> The lame delegations listed above do not refer to root servers.

I'm aware of that, I apologize for not including the relevant entries:
May 17 08:48:40 Lame delegation for "i.gtld-servers.net." from
"192.5.5.241:53"
May 17 08:48:40 Lame delegation for "j.gtld-servers.net." from
"192.5.5.241:53"

Those two do, right?

I also get absolutely blasted by the following folks all the time from
multiple IP addresses:
May 17 08:48:40 Lame delegation for "dns3.cnnic.net.cn." from
"198.32.64.12:53"

> You're seeing a fair number of bogus replies. This can sometimes be
> caused by a malfunctioning (possibly overloaded) router, or by
> overloading Open Transport on the server, and the same condition can
> also cause Open Transport to fail. This could be causing your crash.
> It could also cause the extra DNS reply logged by your mail server.

Given the load on the server (almost all of it from externally) I can
certainly see Open Transport getting overloaded.

Our router is almost never overloaded, that's something I can easily
monitor. What might a misconfiguration look like that would cause an issue
like this?

Thanks,
Dave

----------------------------------------------------------------------------
David R. Cooper
Information Systems Manager
Acton Institute
for the Study of Religion and Liberty

161 Ottawa Avenue NW Suite 301
Grand Rapids, Michigan 49503
phone: 616-454-3080
fax: 616-454-9454

e-mail: dcooper@acton.org
http://www.acton.org/

----------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This communication and any accompanying documents
are privileged. They are intended for the sole use of the addressee. If you
receive this transmission in error, you are advised that any disclosure,
distribution, or the taking of any action in reliance upon the communication
is strictly prohibited. Moreover, any such inadvertent disclosure shall not
compromise or be a waiver of any applicable privilege as to this
communication or otherwise. If you received this communication in error,
please contact the sender at his/her Internet address or by telephone at
616-454-3080. Thank you.

> From: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Date: Mon, 17 May 2004 20:00:01 +0000
> To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Subject: Quickdns-Talk Digest #1688 - 17/05/04
>
> Quickdns-Talk Digest #1688 - Manudagur, 17. mai 2004
>
> "Boot file setup"
> by "Jona Tallieu" <Junk@tnt.be>
> Re: QDNS 3.53 server crash
> by "David Cooper" <dcooper@acton.org>
> license question
> by "Karl Schroll" <schroll@digitalfrontier.com>
> Re: Non-authoritative server
> by "Men & Mice Support" <cbuxton@menandmice.com>
> Re: QDNS 3.53 crash
> by "Men & Mice Support" <cbuxton@menandmice.com>
> Re: "Boot file setup"
> by "Men & Mice Support" <cbuxton@menandmice.com>
> Re: QDNS 3.53 server crash
> by "Men & Mice Support" <cbuxton@menandmice.com>
> Re: license question
> by "Men & Mice Support" <cbuxton@menandmice.com>
>
>
> ----------------------------------------------------------------------
>
> Subject: "Boot file setup"
> From: "Jona Tallieu" <Junk@tnt.be>
> Date: Mon, 17 May 2004 14:35:04 +0200
>
> Hi all,
>
> we are still using QDNS on OS9.
>
> Now, for the first time we are going to be primary for a .FR domains.
>
> We got a mail back from FR-NIC saying that our nameserver is not OK:
>
>
> ----------------------------------------------->
> 4. Miscellaneous Topics
>
> 4.1 Boot file setup
>
> Certain zones should always be present in nameserver configurations:
>
> primary localhost localhost
> primary 0.0.127.in-addr.arpa 127.0
> primary 255.in-addr.arpa 255
> primary 0.in-addr.arpa 0
>
> These are set up to either provide nameservice for "special"
> addresses, or to help eliminate accidental queries for broadcast or
> local address to be sent off to the root nameservers. All of these
> files will contain NS and SOA records just like the other zone files
> you maintain, the exception being that you can probably make the SOA
> <-----------------------------------------------
>
>
> What should we do to make those .FR guys happy with our QDNS server?
>
>
> Thanks!
>
>
> J.
>
> ----------------------------------------------------------------------
>
> Subject: Re: QDNS 3.53 server crash
> From: "David Cooper" <dcooper@acton.org>
> Date: Mon, 17 May 2004 09:04:17 -0400
>
> There's nothing especially informative in the log file right before it
> happened, just the usual assortment of lameness.
>
> May 15 03:27:32 Dropping bogus reply from 204.59.64.222:53
> May 15 03:27:33 Dropping bogus reply from 204.59.144.222:53
> May 15 03:27:33 Dropping bogus reply from 204.59.144.222:53
> May 15 03:27:33 Dropping bogus reply from 204.59.1.222:53
> May 15 03:27:33 Dropping bogus reply from 204.59.1.222:53
> May 15 03:27:33 Lame delegation for "ns1.zptc.co.zw." from
> "194.133.122.47:53"
> May 15 03:27:33 Lame delegation for "ns2.zptc.co.zw." from
> "194.133.122.47:53"
> May 15 03:27:33 Dropping bogus reply from 204.59.64.222:53
> May 15 03:27:34 Dropping bogus reply from 204.59.144.222:53
> May 15 03:27:34 Dropping bogus reply from 204.59.64.222:53
> May 15 03:27:34 Dropping bogus reply from 204.59.144.222:53
> May 15 03:27:34 Dropping bogus reply from 204.59.1.222:53
> May 15 03:27:34 Dropping bogus reply from 204.59.1.222:53
> May 15 03:27:35 Dropping bogus reply from 204.59.64.222:53
> May 15 03:27:35 Dropping bogus reply from 204.59.64.222:53
> May 15 03:27:35 Dropping bogus reply from 204.59.144.222:53
> May 15 03:27:35 Dropping bogus reply from 204.59.1.222:53
> May 15 03:27:35 Dropping bogus reply from 204.59.144.222:53
> May 15 03:27:35 Dropping bogus reply from 204.59.64.222:53
> May 15 03:27:35 Dropping bogus reply from 204.59.1.222:53
> May 15 03:27:36 Dropping bogus reply from 204.59.64.222:53
> May 15 03:27:50 Lame delegation for "36.154.204.137.in-addr.arpa." from
> "137.204.174.6:53"
>
> May 16 13:45:23 Server starting
>
>
> Another question I have is: Why do I get lame delegations from the root
> servers?
>
> Thanks,
> Dave
>
> ----------------------------------------------------------------------------
> David R. Cooper
> Information Systems Manager
> Acton Institute
> for the Study of Religion and Liberty
>
> 161 Ottawa Avenue NW Suite 301
> Grand Rapids, Michigan 49503
> phone: 616-454-3080
> fax: 616-454-9454
>
> e-mail: dcooper@acton.org
> http://www.acton.org/
>
> ----------------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This communication and any accompanying documents
> are privileged. They are intended for the sole use of the addressee. If you
> receive this transmission in error, you are advised that any disclosure,
> distribution, or the taking of any action in reliance upon the communication
> is strictly prohibited. Moreover, any such inadvertent disclosure shall not
> compromise or be a waiver of any applicable privilege as to this
> communication or otherwise. If you received this communication in error,
> please contact the sender at his/her Internet address or by telephone at
> 616-454-3080. Thank you.
>
>> From: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
>> Date: Sun, 16 May 2004 20:00:01 +0000
>> To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
>> Subject: Quickdns-Talk Digest #1687 - 16/05/04
>>
>> Quickdns-Talk Digest #1687 - Sunnudagur, 16. mai 2004
>>
>> QDNS 3.53 crash
>> by "David Cooper" <dcooper@acton.org>
>>
>>
>> ----------------------------------------------------------------------
>>
>> Subject: QDNS 3.53 crash
>> From: "David Cooper" <dcooper@acton.org>
>> Date: Sun, 16 May 2004 14:34:52 -0400
>>
>> With 15 minutes of the following message appearing in our mail server log
>> our QDNS server crashed. I don't have anything from the QDNS server log for
>> that time frame yet but I'm wondering if this message might shed any light
>> on what happened.
>>
>>
>> 03:24:26.49 3 DNR got response from [192.168.0.50] for an unqueued request
>> 2974; discarded
>>
>>
>>
>> It seems fairly straight forward, but by 3:39am it was not responding to
>> requests. Is it more likely that a crash of the DNS server would have
>> triggered the mail server message or rather than some kind of request made
>> of the DNS server by the mail server causing the crash?
>>
>> QDNS 3.53
>> Mac OS 9.1
>>
>> 80MB of RAM allocated to QDNS.
>>
>>
>> Thanks,
>> Dave
>>
>>
>>
>> ----------------------------------------------------------------------------
>> David R. Cooper
>> Information Systems Manager
>> Acton Institute
>> for the Study of Religion and Liberty
>>
>> 161 Ottawa Avenue NW Suite 301
>> Grand Rapids, Michigan 49503
>> phone: 616-454-3080
>> fax: 616-454-9454
>>
>> e-mail: dcooper@acton.org
>> http://www.acton.org/
>>
>> ----------------------------------------------------------------------------
>> CONFIDENTIALITY NOTICE: This communication and any accompanying documents
>> are privileged. They are intended for the sole use of the addressee. If you
>> receive this transmission in error, you are advised that any disclosure,
>> distribution, or the taking of any action in reliance upon the communication
>> is strictly prohibited. Moreover, any such inadvertent disclosure shall not
>> compromise or be a waiver of any applicable privilege as to this
>> communication or otherwise. If you received this communication in error,
>> please contact the sender at his/her Internet address or by telephone at
>> 616-454-3080. Thank you.
>>
>>
>> ----------------------------------------------------------------------
>> End of Quickdns-Talk Digest
>>
>
>
> ----------------------------------------------------------------------
>
> Subject: license question
> From: "Karl Schroll" <schroll@digitalfrontier.com>
> Date: Mon, 17 May 2004 09:40:01 -0400
>
> How does the 4.6.1 license work? I had a primary and a slave server.
> Today, the slave does not appear in Manager, but when I try to add it
> again using Add Name Server, the message is that it "is already in
> use".
>
> I have a valid license for 4.6.1 on Mac X. I had been using a demo
> license. In license manager, both were installed. Today, I launched
> Manager, and was told that one of the licenses had expired (the demo
> license), and to contact sales. So I deleted the demo license.
>
> I presume that my license only allows me to manage the primary
> server, and that I saw the slave before because of the demo license,
> is that correct? So the question is, do I need another license to
> run a slave server? Or is that not needed? When I create a zone in
> the primary and add the slave as a name server, is that info passed
> over to the slave?
>
> --
> Regards,
>
> Karl Schroll
> Digital Frontier
> 802-253-8612
> http://www.digitalfrontier.com
>
> ----------------------------------------------------------------------
>
> Subject: Re: Non-authoritative server
> From: "Men & Mice Support" <cbuxton@menandmice.com>
> Date: Mon, 17 May 2004 11:58:16 -0700
>
> At 7:43 PM -0800 5/13/04, Matthew Fosberg wrote:
>> Here's my results so far:
>>
>> Checked all spelling and for any obvious errors of that sort, and
>> found none, of course it's still possible I'm just not seeing one
>> that is there.
>>
>> I got DNS Expert Pro and queried the server from both the server
>> itself and from another computer on my local network. Both report as
>> receiving authoritative answers from mattcave.bohemianfreecorps.com.
>>
>> I am in the process of having a friend check on what he sees when he
>> connects from his home, but I probably won't find out until
>> tomorrow. Meanwhile, DNSstuff.com still reports my server as being
>> non-authoritative.
>>
>> A couple of things that might have relevance.
>>
>> 1. When I try to log on to the server from the machine itself with
>> QuickDNS manager it will only allow me to do so when I use the
>> internal IP address of the computer it is on 192.168.1.10. If I try
>> the public IP, or the server name I get an error stating I cannot
>> log on to the server.
>
> That generally indicates that your NAT router either isn't set up to
> map the necessary ports (1231 for QuickDNS Central, 1337 for QuickDNS
> Remote), or doesn't permit connections from inside to inside via NAT.
>
>> 2. I am not using this server for my own DNS purposes, (other than
>> providing DNS for one of my domains and a friends) I use my ISP's
>> DNS for my own computers, so nothing inside my personal network
>> should be querying the server. I also do not have the reverse zone
>> configured to point to my static IP, and I know that my ISP will not
>> delegate that to me.
>>
>> Could either of these be related to my problem?
>
> Not number 2. Number 1 might.
> ____________________________________________________________________
> Chris Buxton Men & Mice
> Customer Support Specialist Making DNS Easy
>
>> On May 13, 2004, at 7:15 AM, Men & Mice Support wrote:
>>
>>> Since there's nothing obviously wrong, check every detail. Here's
>>> an example of how you might approach this:
>>>
>>> Step 1: Check the spelling of the zone in QuickDNS Manager.
>>>
>>> Step 2: Download DNS Expert Pro from our FTP server and install it
>>> on the server. If you don't have a license, it will act in demo
>>> mode, which is fine for this testing. Use the DNS Query tool in DNS
>>> Expert Pro to query the server, non-recursively, for any record
>>> named bohemianfreecorps.com. If it doesn't return an authoritative
>>> answer, then the problem is on the server itself. Otherwise,
>>> continue to step 3.
>>>
>>> Step 3: Copy DNS Expert Pro to another machine on the same switch
>>> and repeat the test. If the test in step 2 succeeded, but the test
>>> in this step failed, then the problem is in the switch.
>>>
>>> Step 4: Repeat step 3, moving outward from the server each time.
>>> For example, the next test might be from outside the router (if you
>>> can manage this), or sent through the router to the public IP
>>> address.
>
>
> ----------------------------------------------------------------------
>
> Subject: Re: QDNS 3.53 crash
> From: "Men & Mice Support" <cbuxton@menandmice.com>
> Date: Mon, 17 May 2004 12:01:57 -0700
>
> No matter what query the mail server sent, QuickDNS Server shouldn't
> have crashed. The mail server log message could simply indicate that
> a query was sent, took to long and timed out, and then QuickDNS sent
> back the response. (You'd have to check with the mail server vendor
> to see if this is plausible.)
>
> QuickDNS Server 3.5.3, as far as we know, has no bugs. But Open
> Transport has bugs, and if it crashes, QuickDNS Server crashes. Our
> best advice to you is to upgrade to Mac OS X.
> ____________________________________________________________________
> Chris Buxton Men & Mice
> Customer Support Specialist Making DNS Easy
>
> At 2:34 PM -0400 5/16/04, David Cooper wrote:
>> With 15 minutes of the following message appearing in our mail server log
>> our QDNS server crashed. I don't have anything from the QDNS server log for
>> that time frame yet but I'm wondering if this message might shed any light
>> on what happened.
>>
>>
>> 03:24:26.49 3 DNR got response from [192.168.0.50] for an unqueued request
>> 2974; discarded
>>
>>
>>
>> It seems fairly straight forward, but by 3:39am it was not responding to
>> requests. Is it more likely that a crash of the DNS server would have
>> triggered the mail server message or rather than some kind of request made
>> of the DNS server by the mail server causing the crash?
>>
>> QDNS 3.53
>> Mac OS 9.1
>>
>> 80MB of RAM allocated to QDNS.
>>
>>
>> Thanks,
>> Dave
>>
>>
>>
>> ----------------------------------------------------------------------------
>> David R. Cooper
>> Information Systems Manager
>> Acton Institute
>> for the Study of Religion and Liberty
>>
>> 161 Ottawa Avenue NW Suite 301
>> Grand Rapids, Michigan 49503
>> phone: 616-454-3080
>> fax: 616-454-9454
>>
>> e-mail: dcooper@acton.org
>> http://www.acton.org/
>>
>> ----------------------------------------------------------------------------
>> CONFIDENTIALITY NOTICE: This communication and any accompanying documents
>> are privileged. They are intended for the sole use of the addressee. If you
>> receive this transmission in error, you are advised that any disclosure,
>> distribution, or the taking of any action in reliance upon the communication
>> is strictly prohibited. Moreover, any such inadvertent disclosure shall not
>> compromise or be a waiver of any applicable privilege as to this
>> communication or otherwise. If you received this communication in error,
>> please contact the sender at his/her Internet address or by telephone at
>> 616-454-3080. Thank you.
>
>
> ----------------------------------------------------------------------
>
> Subject: Re: "Boot file setup"
> From: "Men & Mice Support" <cbuxton@menandmice.com>
> Date: Mon, 17 May 2004 12:06:06 -0700
>
> Create 4 zones, one for each of the names they sent (localhost,
> 0.0.127.in-addr.arpa, 255.in-addr.arpa, and 0.in-addr.arpa). I'm not
> sure what they want you to have in the last two, but the first two
> should look something like this:
> ____________________________________________________________________
>
> localhost:
> ==========
>
> @ NS @
> @ A 127.0.0.1
> ____________________________________________________________________
>
> 0.0.127.in-addr.arpa:
> =====================
>
> @ NS localhost.
> 1 PTR localhost.
> ____________________________________________________________________
>
> Those are shown in shorthand notation, without the SOA records (which
> are basically irrelevant for these zones). You can copy these records
> and paste them into the newly-created zones in QuickDNS Manager. Be
> sure to remove any NS records QuickDNS creates for you, as they
> aren't appropriate for these special zones.
> ____________________________________________________________________
> Chris Buxton Men & Mice
> Customer Support Specialist Making DNS Easy
>
> At 2:35 PM +0200 5/17/04, Jona Tallieu wrote:
>> Hi all,
>>
>> we are still using QDNS on OS9.
>>
>> Now, for the first time we are going to be primary for a .FR domains.
>>
>> We got a mail back from FR-NIC saying that our nameserver is not OK:
>>
>>
>> ----------------------------------------------->
>> 4. Miscellaneous Topics
>>
>> 4.1 Boot file setup
>>
>> Certain zones should always be present in nameserver configurations:
>>
>> primary localhost localhost
>> primary 0.0.127.in-addr.arpa 127.0
>> primary 255.in-addr.arpa 255
>> primary 0.in-addr.arpa 0
>>
>> These are set up to either provide nameservice for "special"
>> addresses, or to help eliminate accidental queries for broadcast or
>> local address to be sent off to the root nameservers. All of these
>> files will contain NS and SOA records just like the other zone files
>> you maintain, the exception being that you can probably make the SOA
>> <-----------------------------------------------
>>
>>
>> What should we do to make those .FR guys happy with our QDNS server?
>>
>>
>> Thanks!
>>
>>
>> J.
>
>
> ----------------------------------------------------------------------
>
> Subject: Re: QDNS 3.53 server crash
> From: "Men & Mice Support" <cbuxton@menandmice.com>
> Date: Mon, 17 May 2004 12:11:14 -0700
>
> At 9:04 AM -0400 5/17/04, David Cooper wrote:
>> There's nothing especially informative in the log file right before it
>> happened, just the usual assortment of lameness.
>
> You're seeing a fair number of bogus replies. This can sometimes be
> caused by a malfunctioning (possibly overloaded) router, or by
> overloading Open Transport on the server, and the same condition can
> also cause Open Transport to fail. This could be causing your crash.
> It could also cause the extra DNS reply logged by your mail server.
>
>> May 15 03:27:32 Dropping bogus reply from 204.59.64.222:53
>> May 15 03:27:33 Dropping bogus reply from 204.59.144.222:53
>> May 15 03:27:33 Dropping bogus reply from 204.59.144.222:53
>> May 15 03:27:33 Dropping bogus reply from 204.59.1.222:53
>> May 15 03:27:33 Dropping bogus reply from 204.59.1.222:53
>> May 15 03:27:33 Lame delegation for "ns1.zptc.co.zw." from
>> "194.133.122.47:53"
>> May 15 03:27:33 Lame delegation for "ns2.zptc.co.zw." from
>> "194.133.122.47:53"
>> May 15 03:27:33 Dropping bogus reply from 204.59.64.222:53
>> May 15 03:27:34 Dropping bogus reply from 204.59.144.222:53
>> May 15 03:27:34 Dropping bogus reply from 204.59.64.222:53
>> May 15 03:27:34 Dropping bogus reply from 204.59.144.222:53
>> May 15 03:27:34 Dropping bogus reply from 204.59.1.222:53
>> May 15 03:27:34 Dropping bogus reply from 204.59.1.222:53
>> May 15 03:27:35 Dropping bogus reply from 204.59.64.222:53
>> May 15 03:27:35 Dropping bogus reply from 204.59.64.222:53
>> May 15 03:27:35 Dropping bogus reply from 204.59.144.222:53
>> May 15 03:27:35 Dropping bogus reply from 204.59.1.222:53
>> May 15 03:27:35 Dropping bogus reply from 204.59.144.222:53
>> May 15 03:27:35 Dropping bogus reply from 204.59.64.222:53
>> May 15 03:27:35 Dropping bogus reply from 204.59.1.222:53
>> May 15 03:27:36 Dropping bogus reply from 204.59.64.222:53
>> May 15 03:27:50 Lame delegation for "36.154.204.137.in-addr.arpa." from
>> "137.204.174.6:53"
>>
>> May 16 13:45:23 Server starting
>>
>>
>> Another question I have is: Why do I get lame delegations from the root
>> servers?
>
> The lame delegations listed above do not refer to root servers.
> ____________________________________________________________________
> Chris Buxton Men & Mice
> Customer Support Specialist Making DNS Easy
>
>>> With 15 minutes of the following message appearing in our mail server log
>>> our QDNS server crashed. I don't have anything from the QDNS server log
>>> for
>>> that time frame yet but I'm wondering if this message might shed any light
>>> on what happened.
>>>
>>>
>>> 03:24:26.49 3 DNR got response from [192.168.0.50] for an unqueued request
>>> 2974; discarded
>>>
>>>
>>>
>>> It seems fairly straight forward, but by 3:39am it was not responding to
>>> requests. Is it more likely that a crash of the DNS server would have
>>> triggered the mail server message or rather than some kind of request made
>>> of the DNS server by the mail server causing the crash?
>>>
>>> QDNS 3.53
>>> Mac OS 9.1
>>>
>>> 80MB of RAM allocated to QDNS.
>>>
>>>
>>> Thanks,
>>> Dave
>>>
>>>
>>>
>>>
>>> ----------------------------------------------------------------------------
>>> David R. Cooper
>>> Information Systems Manager
>>> Acton Institute
>>> for the Study of Religion and Liberty
>>>
>>> 161 Ottawa Avenue NW Suite 301
>>> Grand Rapids, Michigan 49503
>>> phone: 616-454-3080
>>> fax: 616-454-9454
>>>
>>> e-mail: dcooper@acton.org
>>> http://www.acton.org/
>>>
>>>
>>> ----------------------------------------------------------------------------
>>> CONFIDENTIALITY NOTICE: This communication and any accompanying documents
>>> are privileged. They are intended for the sole use of the addressee. If
>>> you
>>> receive this transmission in error, you are advised that any disclosure,
>>> distribution, or the taking of any action in reliance upon the
>>> communication
>>> is strictly prohibited. Moreover, any such inadvertent disclosure shall not
>>> compromise or be a waiver of any applicable privilege as to this
>>> communication or otherwise. If you received this communication in error,
>>> please contact the sender at his/her Internet address or by telephone at
>>> 616-454-3080. Thank you.
>>>
>>>
>>> ----------------------------------------------------------------------
>>> End of Quickdns-Talk Digest
>>>
>
>
> ----------------------------------------------------------------------
>
> Subject: Re: license question
> From: "Men & Mice Support" <cbuxton@menandmice.com>
> Date: Mon, 17 May 2004 12:15:01 -0700
>
> Please contact our sales staff about a second license. One license
> covers one server, and the master server can't automatically set up
> the slave server for you.
> ____________________________________________________________________
> Chris Buxton Men & Mice
> Customer Support Specialist Making DNS Easy
>
> At 9:40 AM -0400 5/17/04, Karl Schroll wrote:
>> How does the 4.6.1 license work? I had a primary and a slave
>> server. Today, the slave does not appear in Manager, but when I try
>> to add it again using Add Name Server, the message is that it "is
>> already in use".
>>
>> I have a valid license for 4.6.1 on Mac X. I had been using a demo
>> license. In license manager, both were installed. Today, I
>> launched Manager, and was told that one of the licenses had expired
>> (the demo license), and to contact sales. So I deleted the demo
>> license.
>>
>> I presume that my license only allows me to manage the primary
>> server, and that I saw the slave before because of the demo license,
>> is that correct? So the question is, do I need another license to
>> run a slave server? Or is that not needed? When I create a zone in
>> the primary and add the slave as a name server, is that info passed
>> over to the slave?
>>
>> --
>> Regards,
>>
>> Karl Schroll
>> Digital Frontier
>> 802-253-8612
>> http://www.digitalfrontier.com
>
>
> ----------------------------------------------------------------------
> End of Quickdns-Talk Digest
>

Sales:
888/4-DPOINT

Support:
858/452-3696