[scorpioserve]

[QUOTE][u]Quote by: khiltd[/u][p]I generally avoid the GUI when it comes to configuring BIND, and I don’t believe I’m alone in that practice. What exactly is it you want to accomplish?[/p][/QUOTE]

I have already configured the DNS server through the use of OS X Servers built in GUI, this is a simple DNS setup so it worked great, now that gave me a primary zone and a reverse zone, what I would like to know is when configuring another system to be a secondary DNS Server for this domain, do I have to configure a secondary for the primary only, or do I also need a secondary for the primary’s reverse record.

Hope I have not worded this too badly, thanks for the help

[scorpioserve]

Hmmm, is the question so silly that nobody wants to answer it, or is it so silly that nobody has ever asked it and does not really know. I Wonder 💡

[scorpioserve]

Thanks for the info, I will have to give it a try.

[scorpioserve]

[QUOTE][u]Quote by: premiermac[/u][p]Why don’t you just use Webmin? It’s great for managing a lot of FOSS.[/p][/QUOTE]

Sorry excuse my ignorance but is webmin a fully fledged hosting company’s control panel, like something I would use on a mac if I were to do hosting packages for people. 😳

[scorpioserve]

Thanks Robert, sounds great, I will do a couple reboots and wait for it to start its trouble, get the logs and send you the relative section, thanks for taking the time to help

Regards Paul

[scorpioserve]

Sorry one last thing I forgot to mention is that, and correct me if I am wrong but I thik that the ~ tilda symbol on os X is like an alias pointing to a specific folder, so I would rater use absolute paths for this lot, just incase. 😉

[scorpioserve]

As far as I am aware the 404 error is due to permissions, I think that you might need to add some code into your apache httpd.conf file something like this.
Ok so first the file can be found in your /etc/apache/ directory, the code you are looking for should look something like this.

[code]
#
# Possible values for the Options directive are “None”, “All”,
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that “MultiViews” must be named *explicitly* — “Options All”
# doesn’t give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks MultiViews

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be “All”, “None”, or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride All

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

[/code]

so now what you do is just copy all that code and paste it just below itself like this
[code]
#
# Possible values for the Options directive are “None”, “All”,
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that “MultiViews” must be named *explicitly* — “Options All”
# doesn’t give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks MultiViews

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be “All”, “None”, or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride All

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

/>
#
# Possible values for the Options directive are “None”, “All”,
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that “MultiViews” must be named *explicitly* — “Options All”
# doesn’t give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks MultiViews

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be “All”, “None”, or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride All

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

[/code]

If this still does not work then you may need to also edit the httpd-vhosts.conf file located in the /etc/apache/extra/ directory, and do something like this.
[code]#
# ServerAdmin [email protected]
# DocumentRoot “/usr/docs/dummy-host2.example.com”
# ServerName dummy-host2.example.com
# ErrorLog “/private/var/log/apache2/dummy-host2.example.com-error_log”
# CustomLog “/private/var/log/apache2/dummy-host2.example.com-access_log” common
#[/code]

Just alter the data to suit your needs and uncomment the lines.

The thing I find strange about this, is that I would do hacks like this on a os x client system as I have no other way, but on an os x server 10.5 system with the use of the ServerAdmin application, all this should be avoided, anyway it might be a good test to do, you can always make copies of the files you are about to edit before and just see if it works.
[code]sudo cp -R /etc/apache2/httpd.conf /etc/apache2/httpd.conf.backup
sudo cp -R /etc/apache2/extra/httpd-vhosts.conf /etc/apache2/extra/httpd-vhosts.conf.backup[/code]Then go and edit the original files, with a plain text editor, or bbedit or textwrangler, or if all else fails pico or nano there are a couple of choices.

It should now work, but i am not certain, the only other alternative I can think of might be to add a .htaccess file into the directory you want access to, If all this fails let me know and I will give you the code for that, it is somewhere on my computer, but I do not think you will need to do something as drastic as that unless you wanted to add some redirects or something.

Hope this helps.

Sorry one last thing I forgot to mention is that after editing these files you need to restart apache to see if the changes worked, either through terminal, or though the websharing pref on a client sys, or ServerAdmin stop:start the web service on a Server sys.

[scorpioserve]

There is a way to get rid of the file 0.0.10.in-addr.arpa, what you have to do is, go into terminal and type these commands, I will try to explain as I go. All work done within Mac OS X Server 10.5.7 on an advanced installation.

// Make a backup of the file first, just in-case you would like to revert back at any stage, and rename it with the extension .backup, I like to do this through terminal as I know that it will not change the file permissions, but I always double check anyway.
[code]sudo cp -R /private/etc/dns/publicView.conf.apple /private/etc/dns/publicView.conf.apple.backup[/code]
// with the next command it is just a double check on the files permissions, so just make sure that they match up for the 2 files
[code]ls -l /private/etc/dns/[/code]
// Make sure Server Admin is not open, as we need to edit a file that is needed by the named.conf file as an include to get the view into Server Admin of all your zones

// Now you need to edit the file publicView.conf.apple like this
[code]sudo pico /private/etc/dns/publicView.conf.apple[/code]
// This will open the requested file into the pico text editor, you need to delete these lines of code in this file.
[code] zone “0.0.10.in-addr.arpa.” {
type master;
file “db.0.0.10.in-addr.arpa.”;
allow-transfer {none;};
allow-update {none;};
};[/code]
once this has been deleted you can use the “WriteOut” command and save your changes to the file, make sure you keep the name as it was so it will overwrite the correct file, then “exit” out of the pico text editor.

Now go to Server Admin and the extra zone should no longer be there.

Hope this helps anybody that was bothered by this extra entry in Server Admin.

[Author]

Posts