Cannot load webpage - DNS Error

[Citimouse]

Hi All,

I am not too sure about DNS and hope any kind soul out there can help me.

We have point all our workstations and servers to our internal DNS server.
They still can surf the internet without any problem. However, when they
surf a particular webpage http://abcd.com/report, it return a DNS error.
This
webpage is located in our offsite data center. When we do a nslookup on
abcd.com, it can return a result. Ths DNS settings in our DHCP server is the
primary DNS points to our local DNS and the secondary DNS points to our ISP
DNS server. So all workstations will get the primary DNS point to our local
DNS and the secondary DNS points to our ISP DNS server.

When we change the workstation primary DNS to point to our ISP DNS server,
the page can load successfully.

I believe I must do some config in my DNS server but I do not know what to
do.

Can someone please help me?

Thanks.

Best Regards,

WY

 

[Deji Akomolafe]

It appears that you are using abcd.com for both your internal and your
external domains, but the zone information is different on both DNS servers.
I mean you maintain 2 different DNS zones - one at your ISP and one on your
internal DNS server for the domain abcd.com. The ISP's DNS server knows the
web server hosting abcd.com, but your internal DNS server does not, probably
because abcd.com is your AD domain name. this is why you are able to access
abcd.com when you sitch DNS to your ISP's DNS server.

If I have been correct so far, then I suggest you start from the obvious
place first: Don't use your ISP's DNS server in your DHCP or anywhere in
your internal AD domain. Second, because your AD domain name and your
external domain name are identical, you will really continue to have this
problem you are seeing. What I would suggest is that you create another
record (like "www") in the abcd.com zone and use that for accessing your
website. You will need to do this on both the external DNS server and the
internal DNS server. I know there have been some other recommendations for
this issue in this newsgroup, and I have no doubt that those will work also,
but I personally will not offer those recommendations because I don't like
them.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
MVP - Directory Services
www.readymaids.com - got SPAM problems?
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon

 

[Kevin D. Goodknecht [MVP]]

In

It appears that you are using abcd.com for both your internal and your
external domains, but the zone information is different on both DNS
servers. I mean you maintain 2 different DNS zones - one at your ISP
and one on your internal DNS server for the domain abcd.com. The
ISP's DNS server knows the web server hosting abcd.com, but your
internal DNS server does not, probably because abcd.com is your AD
domain name. this is why you are able to access abcd.com when you
sitch DNS to your ISP's DNS server.

If I have been correct so far, then I suggest you start from the
obvious place first: Don't use your ISP's DNS server in your DHCP or
anywhere in your internal AD domain. Second, because your AD domain
name and your external domain name are identical, you will really
continue to have this problem you are seeing. What I would suggest is
that you create another record (like "www") in the abcd.com zone and
use that for accessing your website. You will need to do this on both
the external DNS server and the internal DNS server. I know there
have been some other recommendations for this issue in this
newsgroup, and I have no doubt that those will work also, but I
personally will not offer those recommendations because I don't like
them.

Just to clarify, if your Active Directory domain name is abcd.com, you must
be aware that for all clients that are members of the AD domain, abcd.com
must resolve to IP addresses on Domain Controllers that have file sharing
enabled. It is this IP address that the Sysvol DFS share is bound to, it is
this share that Group Policies are applied from in
\\abcd.com|SYSVOL\abcd.com\policies . If you change the behavior so that the
name resolves to the IP of the website for abcd.com then all member clients
and servers will try to find the Sysvol DFS share on the web server, not a
good situation. Therefore, I agree with Deji, configure the site to be
available at www.abcd.com/reports You can however configure a web site in
IIS on the DCs to redirect page by page directory by directory to
www.abc.com/<whatever> of course depending on the number of pages and
directories it will be easier to instruct users to use www before the domain
name.