DNS Server is timing out using forwarder

[kevin roberts]

I have my DNS server network setting pointing to its own
ip (10.0.1.25) The DNS server only listens on that ip.
The forwarders are resolver.qwest.net and ns.cw.net. If i
do a nslookup on most domains its fine. If i do an
nslookup on aol.com i get the desired results, however
when i change the type to mx and query my server i get a
time out everytime. If i change the server for nslookup
to either of the above i get the mx records. Right now my
network setting reflect the two above servers because the
forwarder does not appear to be working.

It seems like it is only AOL MX records that are having
the issue how do i fix this ?

[ObiWan]

Uhm ... try allowing TCP DNS queries (dest.port=TCP/53)
and see if this solves your problem, the AOL MX list is
somewhat "big" so I suspect that the DNS tries UDP and
then since the data won't fit into a single UDP packet tries
again with TCP ... and if TCP isn't allowed ... it fails

--

* ObiWan

DNS "fail-safe" for Windows 2000 and 9X clients.
http://ntcanuck.com

408 XP/2000 tweaks and tips
http://ntcanuck.com/tq/Tip_Quarry.htm

[Jonathan de Boyne Pollard]

kr> It seems like it is only AOL MX records that are having
kr> the issue how do i fix this ?

If this is Windows DNS Server 2003, then the problem could well be that your
server is telling 205.171.3.65 and 204.70.128.1 to use large DNS/UDP datagram
sizes with EDNS, but your router or firewall is then discarding any such
packets.

To fix, disable EDNS.