Oh-ho, you are trying to serve web pages from a domain with the same name as your AD's FQDN. That was an important omission.
Unless you have a really compelling reason to do this, the simplest course of action is not to do this. Pick another name for the website, tool around with your clients' DNS search suffixes, etc. Internal clients should not have the expectation of going to "adfqdn.local" and getting a website. Hopefully your AD domain does not have the same name as the organization's public presence. You could suppress AD's automatic A records for the domain, but this is not a good way of fixing the purported problem. --Steve On Mon, May 7, 2012 at 7:52 PM, Juned Shaikh <jsha...@gmail.com> wrote: > so www record exist and 2) yet another A record which is point to the domain > <example.com> both exist. > > NSLOOKUP of www record show correct IP address > > however NSLOOKUP of domain <example.com> finds all AD DNS Servers.. (expected > as all servers are AD integrated DNS server) > > This proves that although the A record point to www exist and saperate www > record exist however it is nullify since domainname is taken over by being AD > integrated DNS. > > What is the possible workaround? in this event? > > Thanks, > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
