 |  |
At 10:37 PM -0700 6/29/04, Scott Haneda wrote:
Re: Upgraded to OS X, have some questions...
From: Men & Mice Support
Date: Tuesday, June 29, 2004
Time: 10:59:15 pm
>Thanks for the answers Chris, I have a few questions still.
>
>on 06/29/2004 10:14 PM, Men & Mice Support at cbuxton@menandmice.com wrote:
>
>> At 4:05 PM -0700 6/29/04, Scott Haneda wrote:
>>> A few questions:
>
>>> I did add a new A record to the server, dig's on that and got back a
>>> response, so I assume it is working, but the logs don't tell me so. (I am
>>> using the log viewer in the admin app)
>>>
>>> If I wanted to add a new primary zone via the CLI, how would I do this?
>>
>> Do you have an enterprise license? If so, you can use QuickDNS
>> Manager/CLI - instructions for adding a zone are in the documentation.
>>
>> Otherwise, adding a new zone via the CLI isn't generally considered a
>> good idea. If necessary, though, you can do it as follows (do
>> everything as root, or set the ownership of the files you create to
>> root) (I'm assuming QuickDNS 4.6.1 on Mac OS X 10.3):
>
>Basically, While I want to use QDNS for ease of use, I also don't want to
>limit my abilities to manage other machines that may be just running BIND
>with no front end to config it, so I would be left with ssh access and some
>text editor.
Ah. In that case, add a zone statement to the configuration in the
appropriate place (start by looking in /etc/named.conf). Then put the
zone file wherever the system normally stores them. Then load it in
using the rndc command I gave before.
>Just out of curiosity, can one set up a QDNS server, uninstall QDNS and have
>bind just pick up all alone with no QDNS at all?
Sure.
> > The zone casarta.com on the master server has an error. Fix it on the
> > primary master server.
>
>Easier said than done, when I try to open this zone it errors "Error opening
>zone file "hosts/slaves/casarta.com-hosts".
>
>This is just a slave zone, I guess there is something wrong on the remote
>master server? What would I look for?
Yes. That's why I said, "Fix it on the primary master server." Look
for all CNAME records, and compare their names against the names of
the rest of the records. There should be no overlap between the two
sets.
> >> Jun 29 15:58:51.859 config: error: /var/named/conf/logging:33: unknown
> >> logging category 'statistics' ignored
>>
>> This is a cosmetic issue caused by the QuickDNS 4.6.1 installer. Edit
>> /var/named/conf/logging (as root) and remove the lines referencing
>> these logging categories. (The line numbers are listed in the error
>> messages.) Then:
>>
> > sudo rndc reconfig
>
>If it is cosmetic, I don't so much care, is there a file I can just copy and
>paste from rather than looking up the data in the log and then finding out
>which lines to remove?
You could remove all of the category statements, and then go back
into Server Options in QuickDNS Manager and check all of the
categories you want logged. Note that there's a channel selector at
the top of the logging pane - this selects which channel you're
editing, not which one is "active". All channels are used by named at
all times.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy
Messages In This Thread:
Return to Digital Point Solutions' Home Page
| home | |
| products | |
| services | |
| support | |
| email lists |
| optigold isp | |
| optigold isp news | |
| home inspection | |
| inspectrix | |
| java companion | |
| oracle | |
| quickdns pro | |
| search engine | |
| veterinary |
| tips | |
| employees | |
| free tools | |
| portfolio | |
| jobs | |
| contact |
888/4-DPOINTSupport:
858/452-3696