Search Again:

Re: Upgraded to OS X, have some questions...

From: Men & Mice Support
Date: Tuesday, June 29, 2004
Time: 10:16:14 pm

At 4:05 PM -0700 6/29/04, Scott Haneda wrote:
>I just installed the demo of QuickDNS on OS X here on my local lan on a
>spare computer.
>
>First, I installed remote and central on the server, then admin on my
>desktop.
>
>I ran the export script from my OS 9 server, copied that over and ran the
>import script, seems that it all went in just fine, even the slaves as well.
>
>A few questions:
>Dig host.com @192.168.1.106 shows the result just fine, but how do I know it
>is really talking to 192.168.1.106 and that this DNS server is working? I
>looked at the log and I see no mention of my query at all?

Use the +norecurse option on the dig command line. Then look at the
bottom of the result - it will tell you what server it queried.

If you want to see queries in the log, set the logging severity level
to "info" and turn on query logging (in the list of checkboxes at
right).

>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):

- Put the zone file, with Unix line endings, in
/var/named/hosts/masters. Name the file "zone.name-hosts".

- Put a zone options file in /var/named/conf/zoneopt. Name the file
"zone.name.opt". The file should have the following contents:

zone "zone.name" IN {
type master;
file "hosts/masters/zone.name-hosts";
};

- Add an entry to /var/named/conf/zones like this:

include "conf/zoneopt/zone.name.opt";

- Tell named to load the zone:

rndc reconfig

- Restart QuickDNS Remote:

/Library/StartupItems/QuickDNS/qdnsr restart

>If I wanted to add a new secondary slave via the CLI, how would I do this?

Change the previous as follows:

- Don't create a zone file manually. named will do this for you.

- The zone options file should contain:

zone "zone.name" IN {
type slave;
file "hosts/slaves/zone.name-hosts";
masters { ip.add.re.ss; };
};

- Do everything else the same.

>There are also a good amount of errors in the logs:
>Jun 29 15:56:47.869 xfer-in: error: transfer of 'mayo-family.com/IN' from
>217.155.168.149#53: failed while receiving responses: REFUSED
>Jun 29 15:56:47.872 xfer-in: info: transfer of 'mayo-family.com/IN' from
>217.155.168.149#53: end of transfer

The master server of mayo-family.com refused the zone transfer request.

>Jun 29 15:56:57.805 xfer-in: error: transfer of 'casarta.com/IN' from
>66.196.253.180#53: failed while receiving responses: CNAME and other data
>Jun 29 15:56:57.806 xfer-in: info: transfer of 'casarta.com/IN' from
>66.196.253.180#53: end of transfer

The zone casarta.com on the master server has an error. Fix it on the
primary master server.

>Jun 29 15:57:06.396 general: info: zone newgeo.com/IN: loaded serial
>2004062901
>Jun 29 15:57:06.397 notify: info: zone newgeo.com/IN: sending notifies
>(serial 2004062901)

Not an error.

>wn logging category 'db' ignored
>Jun 29 15:58:51.858 config: error: /var/named/conf/logging:16: unknown
>logging category 'eventlib' ignored
>Jun 29 15:58:51.858 config: error: /var/named/conf/logging:18: unknown
>logging category 'insist' ignored
>Jun 29 15:58:51.858 config: error: /var/named/conf/logging:20: unknown
>logging category 'load' ignored
>Jun 29 15:58:51.858 config: error: /var/named/conf/logging:21: unknown
>logging category 'maintenance' ignored
>Jun 29 15:58:51.858 config: error: /var/named/conf/logging:22: unknown
>logging category 'ncache' ignored
>Jun 29 15:58:51.858 config: error: /var/named/conf/logging:25: unknown
>logging category 'os' ignored
>Jun 29 15:58:51.859 config: error: /var/named/conf/logging:26: unknown
>logging category 'packet' ignored
>Jun 29 15:58:51.859 config: error: /var/named/conf/logging:27: unknown
>logging category 'panic' ignored
>Jun 29 15:58:51.859 config: error: /var/named/conf/logging:28: unknown
>logging category 'parser' ignored
>Jun 29 15:58:51.859 config: error: /var/named/conf/logging:31: unknown
>logging category 'response-checks' ignored
>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
____________________________________________________________________
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

Sales:
888/4-DPOINT

Support:
858/452-3696


Search:
Add this to your site