DNS over WAN Link

[Guest]

I am trying to convince a customer that they need to have one DNS at every
site, because DNS can't resolve names to IP over WAN link. They think it's a
router issue. I tell them no, it's a dns issue. I need to show them that they
need to have at least one dns at every site that coordinate with the dns at
the HQ. Any articles or white papers on this would be appreciated. You can
email me at (e-mail address removed). Thanks,

 

[Guest]

I am trying to convince a customer that they need to have one DNS at every
site, because DNS can't resolve names to IP over WAN link. They think it's a
router issue. I tell them no, it's a dns issue. I need to show them that they
need to have at least one dns at every site that coordinate with the dns at
the HQ. The network is running all Windows 2000 servers and workstations.
So, WINS wouldn't help there. Each physical site has its own subnet:
192.168.1.0, 192.168.2.0, 192.168.3.0 etc... There are Cisco routers between
the sites. There is a DNS and a DHCP for internal name resolution at the
192.168.1.0 subnet. Other sites lack DNS and DHCP servers. Other sites cannot
do name resolution. But if you manuallt hard code their IPs, then they can
see the 192.168.1.0 network and be seen by 192.168.1.0 network. Any white
papers on a situation like this? Any articles or white papers on this would
be appreciated. You can email me at (e-mail address removed). Thanks,