event 7063 - listed forwarders not in list of forwarders

[Tom Rodgers]

I keep getting event 7063 in my DNS logs. the message
reads
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 7063
Date: 10/8/2003
Time: 11:41:43 AM
User: N/A
Computer: NOVADC1
Description:
The DNS server is configured to forward to a non-recursive
DNS server at 192.12.94.30.

DNS servers in forwarders list MUST be configured to
process recursive queries.
Either
1) fix the forwarder (192.12.94.30) to allow recursion
- connect to it with DNS Manager
- bring up server properties
- open "Advanced" tab
- uncheck "Disable Recursion"
- click OK
OR
2) remove this forwarder from this servers forwarders
list
- DNS Manager
- bring up server properties
- open "Forwarders" tab
- remove (192.12.94.30) from list of forwarders
- click OK

The various events list different forwarders, none of
which are configured on my server. I have no idea where
these are coming from. I have only 2 forwarders
configured, both my ISP name servers.

Can anyone tell me where this info is coming from or how
to stop these error messages?

Thanks in advance,

Tom

 

[Tom R]

I found some other posts regarding this issue and
understand that my ISP name servers may be set for
recursion and causing these messages. These events
apparently don't indicate a serious problem but if anyone
has a specific way to prevent them it would be
appreciated. I have changed some logging options and if
not explained below, I have unchecked use recursion on the
forwarders tab.

Thanks,

Tom

 

[Michael Johnston [MSFT]]

Make sure that recursion is not disabled on your servers. On the forwarders tab, make sure that Do Not use Recursion is unchecked. Then on the Advanced
tab, make sure the Disable Recursion is not check either.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.

 

[Mike]

I'm having similar issues since yesterday, Event id 7063. Not being
the only admin I'm not completely sure if anyone else has done
anything but this is how we are setup.

We have multiple internal DNS servers and this happens on two of them.
I have been forwarding to the same ISP DNS servers for years. The
IP's listed are NOT in my list of forwarders for either sever.
However, I did notice that the two servers in question forward to each
other. Isn't that bad?? They host two different zones but have
copies of each others zone. How do the random Ip's referenced show up
in the event id??

I don't have any recursion settings disabled on either server.

These two servers also have the root hints primed. They do forward to
internet.

What I have noticed is that when this happens that some DNS queries
will start to return bogus information.

 

[Ace Fekay [MVP]]

In

I'm having similar issues since yesterday, Event id 7063. Not being
the only admin I'm not completely sure if anyone else has done
anything but this is how we are setup.

Event ID 7063 means that you are forwarding to a DNS server that does not
support forwarding. That's all. Try using 4.2.2.2 as a forwarder. That
works. Forwarding, depending on your design, should be configured
individually on each DNS server. If you have a delegation, that changes the
picture.
http://www.eventid.net/display.asp?eventid=7063&source=

Delegation means if you have a root domain and a child domain, you would
delegate the child domain's DNS as authorative for that domain from the root
doman's DNS servers. Then in the child domain's DNS servers, you would
forward back to the root domain DNS servers and they would forward to the
ISP. Otherwise, configure each DNS individually to the ISP.

We have multiple internal DNS servers and this happens on two of them.
I have been forwarding to the same ISP DNS servers for years. The
IP's listed are NOT in my list of forwarders for either sever.

They should be configured individually unless delegation is in place.

However, I did notice that the two servers in question forward to each
other. Isn't that bad??

Oh YES this is BAD, unless you are in a delegation scenario. If not in a
delegation, then this WILL cause a forwarding loop.

They host two different zones but have
copies of each others zone. How do the random Ip's referenced show up
in the event id??

Not sure about the "random" IPs. but since each have copies of each other,
the looping can occur.

I don't have any recursion settings disabled on either server.

These two servers also have the root hints primed. They do forward to
internet.

"Primed"? That;s not a term associated with DNS. You probably mean they are
available under the Root Hints tab, which is normal.

What I have noticed is that when this happens that some DNS queries
will start to return bogus information.

Change the forwarding from each other to the ISP's.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Mike]

I do have a few delegations setup on one of the servers in question
and I actually have them setup properly based on what you described.
The delegations point back to some other DNS server not involved in
this problem.

The other DNS server in question has no delegations, it just hosts
multiple zones.

What it looks like someone did on these two servers was setup
fordwarders for our ISP which is ok and also to each other, which is
BAD!! since these two don't have delegations to each other.
I will definitely correct the problem on forwarding to each other by
removing the proper IP address from the forwarders tab. I thought
that was a bad thing. Thanks for confirming that for me.

As far as the event id 7063, I have never seen this before. Maybe
correcting my forwarding entries will resolve it. I'm sure my ISP
servers are ok but I guess you never know. Maybe I'll try the 4.2.2.2
you mentioned.

The "random" ip's I mentioned were just the ones listed in the 7063
event id. Like other's who have posted on this problem I was confused
as to how they were even involved in the problem.

Many thanks for your help.

 

[Ace Fekay [MVP]]

In

I do have a few delegations setup on one of the servers in question
and I actually have them setup properly based on what you described.
The delegations point back to some other DNS server not involved in
this problem.

The other DNS server in question has no delegations, it just hosts
multiple zones.

What it looks like someone did on these two servers was setup
fordwarders for our ISP which is ok and also to each other, which is
BAD!! since these two don't have delegations to each other.
I will definitely correct the problem on forwarding to each other by
removing the proper IP address from the forwarders tab. I thought
that was a bad thing. Thanks for confirming that for me.

As far as the event id 7063, I have never seen this before. Maybe
correcting my forwarding entries will resolve it. I'm sure my ISP
servers are ok but I guess you never know. Maybe I'll try the 4.2.2.2
you mentioned.

The "random" ip's I mentioned were just the ones listed in the 7063
event id. Like other's who have posted on this problem I was confused
as to how they were even involved in the problem.

Many thanks for your help.

No prob for the help. Forwarding to each other can cause many odd problems,
worse of which resolution fails. The 7063 errors usually just says it's a
bad (or recursion disabled on it) forwarder.



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory