Forward not working in Bind

We are not able to forward requeses to the servers listed:

zone "xxx.com" IN {
       type forward;
       forwarders { xxx.xxx.104.13; xxx.xxx.104.40; };
};
axl13Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AdraenyseCommented:
Can you post the Options portion of your configuration, and what leads you to believe that it is not working?
0
axl13Author Commented:
options {
#
        directory       "/var/named";
        pid-file        "/var/named/named.pid";
        allow-transfer { xxx.xxx/16; };
        transfer-format one-answer;
        };
logging {
        channel my_file {
                file "/var/named/dns.log";
                severity dynamic;
                print-category yes;
                print-severity yes;
                print-time yes;
                };
#       category default { my_file; };
        category update { my_file; };
        category notify { my_file; };
        category xfer-in { my_file; };
        category xfer-out { my_file; };
#       category security { my_file; };
#       category queries { my_file; };
        };

nslookup turns up server cant find domain: Non-existent domain
0
axl13Author Commented:
Still not able to get FORWARD to work...
0
AdraenyseCommented:
You have no forwarders in your options. Do you have a root hints zone? If not, there is no where for bind to look up any information.


In your options section you need a forwarders statement such as:

forwarders      { 208.67.222.222; 208.67.220.220; };

(These are the OpenDNS servers. I prefer them over any of my ISP servers as they are more reliable and answer faster. http://www.opendns.com/)
Not directly related to your question, but I would recommend also having an allow-recursion statement in your options section for your local subnets or bind will not fully resolve queries for your local machines.

allow-recursion { 127.0.0.1; xx.xx.xx.xx/16; };

Using the statement forward first in the options section will tell bind to try your forwarders first, and if unsucessful, then proceed to query the root zone servers for an answer.

forward first;

If you do not have a root hints zone, this is how you create one

- Connect to ftp.internic.net as anonymous and download domain/named.root- Place named.root in your /var/named directory and chown it named.named and chmod it to 444
- Add the following zone statement to named.conf (outside of the options statement of course)

zone "." { type hint; file "named.root"; };

Hope that helps
Adrae
0
axl13Author Commented:
We could not get the forwarding to work, so we had the users seconday the zone
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.