Re: One DC can't resolve all external addesses

Hank Arnold wrote:
> I have a strange one.... We have two DC's in our W2K domain. First a
> bit of history:
>
> We originally had our only DC (with DHCP and DNS) running Exchange
> 5.5. When I came on board we determined that we needed to address
> this. We set up a new DC and transferred all the FSMOs to it and set
> up integrated DNS and DHCP on it. We then set up a second new DC and
> go it running. Then we DCPROMOd the original server to a member
> server. Everything seemed to be running great.
>
> Recently, I was getting a suspicion that the first DC (with all the
> FSMOs) was not resolving external addresses correctly. I examined the
> DNS settings for both servers and couldn't see any differences at
> all. By making sure that all the workstations and servers had both of
> them specified in the TCP/IP settings, we encountered no problems for
> several months.
>
> In the past week, though, two problems came up. The first was with an
> external web site (a credit union) where we would get "Unable to
> display page" when we tried to go to the web site. This started last
> Thursday. It worked fine from a different ISP. Interestingly, on
> Monday, We could get to the web site and display any page that didn't
> involve a secure connection.
>
> Last week, we also "activated" a new redesigned external web site
> that is hosted for us. by another ISP. However when we would access
> the site, we would get the "old" site... Again, using a different ISP
> than the one we get out internet connection through results in the
> correct page.
>
> If I changed a workstation to use the external DNS sites our DNS uses
> as forwarders, I can access the correct web page.
>
> Now, this is where it gets interesting. We have two DC's,
> 192.168.1.111 (the original w/FSMOs) and 192.168.1.112. If I specify
> the DNS search order as 112 and then 111, we get the correct web
> pages. If I order then as 111 and then 112, we get the "old"
> pages.....
>
> As I said, I can't see any differences between the two. The "111" DC
> also serves as the VPN server and the DHCP server.
>
> Sorry for the long winded post, but I thought the details would help
> in figuring out what is going on.... I would appreciate any
> suggestions on where to look.... TIA.

Did you try restarting the DNS service on that DC to clear any incorrect
cached records?
Is the web site within the same name tree as your internal domain?
You should turn off friendly HTTP errors so you can see the exact error.
With friendly HTTP errors turned it is more difficult to diagnose these
problems because friendly errors are only a general information.

You should also run nslookup against each server to verify whether you get
the right or wrong IP address.


--?
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


.