DNS not doing recursive lookups

I originally posted my question to microsoft.public.windows.server.migration.
Someone suggested that this group would be more appropriate.

To recap:

I took an NT PDC that was hosting a primary DNS for the top-level country
code domain FM and migrated it to a Windows 2003 DC with the single-level AD
domain "FM". DCPROMO installed the DNS and migrated over all the forward and
reverse zones from the NT installation. I manually added the SRV records from
NetLogon.dns to support AD.

The DNS will correctly resolve names for all records hosted in the server's
zone files. However, when asked to resolve a name outside its scope (such as
www.yahoo.com), it fails.

Prior to the migration, DNS on the server was working correctly. In the
network, I have a NT BDC that is the secondary DNS for all the zones hosted
on the primary server. It continues to function normally.

I copied the root hints from the operational secondary DNS server, so I'm
reasonably sure they are valid.

I do not have a root (.) zone defined.

I am not running Windows Firewall, but my Cisco router is doing some
filtering for traffic coming into this server. It is allowing TCP and UDP
traffic on port 53. The same criteria is being applied to my secondary server
as well.

NSLookup tests to remote DNS servers fail when performed on either Windows
2003 primary DNS machine or the NT secondary DNS machine. If I run the same
tests from a machine that does not have any filtering defined at the router,
then the ns lookup tests will succeed.

Anyone have any ideas?
.

Relevant Pages

  • Re: DCDIAG DNS Failure
    ... Without advance view I have 4 forward lookup zones and 7 reverse ... My DNS server is not multihomed. ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... Without advance view I have 4 forward lookup zones and 7 reverse ... do you need all these reverse zones or your DNS server is multihomed ... -Your exchange server that is giving you problems, can it send Mail outside, ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... also can you check if the DNS server is responding to all its IPAddress ... zone and forward zones. ... did you created MX records for the exchange domains that you're hosting? ...
    (microsoft.public.windows.server.dns)
  • RE: SBS2003: Intermitent Connectivity from Clients to Public websi
    ... I already had two zones set up under the Forward Zones. ... names along with their respective IP addresses per DNS name. ... Originally, I did install ISA Server, but uninstalled it. ... you can access them normally on SBS. ...
    (microsoft.public.windows.server.sbs)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
Loading