Multiple DNS Forwards

[Barry Margolin]

In article <cSdZ4.75$WA.16422 at sapphire.mtt.net>,
Dave Walsh <dave_j_walsh at keane.com> wrote:
>I think you're on to something.  I've changed the order of my forward zones
>as you suggested (essentially just switching hal.us.partnerco.com with
>partner.com).  Now I can resolve names in hal.us.partnerco.com, but not
>partner.com as I could before.  I don't know why this is.  It seems as
>though I can only have one forwarder?

You're still missing some semicolons.  There should be a semicolon after
every close curly-brace, i.e. every '}' should be followed by ';'.  I don't
see a semicolon at the end of either line that begins with "forwarders".
Are you still claiming that they're in the real file but being deleted when
you post the message to the newsgroup?  I find it difficult to believe that
your software just deleted two semicolons but left all the rest intact.

>EXAMPLE: named.conf
> =====================
> options {
> directory "/var/named";
> forwarders { 227.252.18.10; };
> forward only;
> query-source address * port 53;
> };
>
>zone "0.0.127.IN-ADDR.ARPA" in {
>type master;
>file "db.127.0.0";
>notify no;
>};
>
>zone "mycompany.ca" in {
>type master;
>file "db.mycompany";
>};
>
>NOTE:   THIS USED TO BE SECOND.  NOW IT'S FIRST ON THE FORWARD LIST AND I
>CAN RESOLVE NAMES IN THE HAL.US.PARTNERCO.COM.  BUT NOW I CAN'T RESOLVE THEM
>IN THE PARTNER.COM BELOW.
>zone "hal.us.partnerco.com" {
>type forward;
>forward only;
>forwarders { 158.138.120.22; }
>};
>
>NOTE:  NOW THAT THIS IS SECOND, I CAN'T RESOLVE NAMES IN PARTNER.COM.
>zone "partner.com" {
>type forward;
>forward only;
>forwarders { 158.138.120.22; }
>};

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.