TheWellington's questions

I am trying to use unbound to forward requests to a pair of dns servers, while answering a small hand full of queries locally. In testing this out, I have built the following configuration at /etc/unbound/conf.d/my.zone.com.conf

forward-zone:
    name: "my.zone.com"
    forward-addr: 1.2.3.4   # my DNS server
    forward-addr: 1.2.3.5   # my other DNS server

    local-data: "server1.my.zone.com. IN A 1.2.3.6"

    local-data-ptr: "1.2.3.6 server1.my.zone.com"

When running unbound-checkconf I get the following error:

$ unbound-checkconf
/etc/unbound.conf.d/my.zone.com.conf:8: error: syntax error
read /etc/unbound.conf.d/my.zone.com.conf failed: 1 errors in configuration file
$

My desired behavior is that unbound should forward all requests to the DNS servers 1.2.3.4, and 1.2.3.5, but should respond with local information for server1.my.zone.com.

I have looked through a number of lengthy config file examples on line, but I just don't see what I am doing wrong - though I suspect it has to do with local-data and local-data-ptr nested inside forward-zone.

The config file at /etc/unbound/unbound.conf remains unchanged from the default yum install in centos7.

Thanks in advance for your help

How do I create and exception to a puppet catalog?

Specifically I want to use Puppet to manage a one-off set of firewall rules, to be combined with the default ruleset.

This is for a single legacy system only, it should get the default set of rules, AND several additional rules.

It seems silly to me to put this on the puppet master, since it truly will only ever be a one-off thing... Can I put this in the modules directory on the local machine? Will Pupped comile a catalog from the server and from the local machine?

Thanks for your help

Bill

I am trying to set up dynamic environments using http://puppetlabs.com/blog/git-workflow-and-puppet-environments/ as a guide. Unfortunately I am not entirely clear on what I am doing.

I have created a directory on the puppet master at /etc/puppetlabs/puppet/environments/

I have copied the configuration examples from the document above to the puppet.conf file on my puppet master. I added the three lines in each section of the document to the respective section of the puppet.conf file, and made changes to suit my system (paths, etc...) Prior to these changes I was working with the default-post-installation copy of puppet.conf

now when I try to run puppet agent -t --noop from a client machine, or from the server I get the following error.

err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class pe_compliance for puppet-test-01.mydomain.net on node puppet-test-01.mydomain.net
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

If I get rid of all that stuffs and put in an enviornment manually in the puppet.conf file on the master, then I can add environment = testenv to the puppet.conf file on the client and I think I get a new environment... but I don't see any such thing in the web UI... so I don't know for sure if this is working either.

What am I doing worng? what do I need to do next

I would like to monitor a few hundred hosts using Nagios, yet I only want the switch fabric to show up in the statusmap.cgi. Is there a way to prevent a host from showing up in the status map, yet have it still be monitored?

I am the administrator of a fairly large laptop program. When browsing my Windows network, I notice an old Windows Domain name and several workgroups.

How do I locate these extra workgroup/domains and expunge them from the system?

The domain in particular was decommissioned four years ago. There is nothing here that should be supporting that name, in fact there are no computers still around that used that domain name.