Bballrball | 2012-07-18 08:42:57
Just upgraded to Windows 2003 server and installed DNS w/AD integration. I have forwarders to my ISP’s DNS servers. I have a network with NT, 2000, and XP clients. Point-to-points between my branches with Cisco 2600 as a core and 1720’s at the edge. When a user from an outlying branch tries to access the internet, the DNS times out. The main branch carries the T-1 internet with a Netscreen firewall(UDP&TCP 53 are open as well as 135). The network scheme is as follows
Main branch 10.0.16.x (Where the DNS server resides
Branch A 10.0.18.
Branch B 10.0.19.
All 10.0.16.x machines can access DNS and get to the internet. The outside of the 16.x subnet are unable to resolve any external DNS.
Bballrball | 2012-07-18 08:43:31
Doing a NSLOOKUP actually returns my name server and if I do one for my ISP it resolves it as well… Also, resolves www.google.com.
Strange. The computers are showing up in the forward and reverse as pointers…so it’s registering correctly. However, still not giving me a website. It just times out.
Bballrball | 2012-07-18 08:43:39
DNS server giving error event ID 7050 (The DNS server recv() function failed. The event data contains the error.)
and event id 5502 (The DNS server received a bad TCP-based DNS message from 10.0.19.61. The packet was rejected or ignored. The event data contains the DNS packet.)
Jonathan de bo 2012-07-26 09:32:04
b> Point-to-points between my branches with Cisco 2600 as a
b> core and 1720’s at the edge.
b> When a user from an outlying branch tries to access the internet,
b> the DNS times out.
How do you know that this is the case and that it is the DNS lookup
that is timing out ?