Browsing Microsoft Websites on a Server 2003 Domain Controller

Hi,

All DNS resolutions for Microsoft websites in the domain microsoft.com eg.
www.microsoft.com www.support.microsoft.com are directed to the local DNS
Server. If this DNS Server isn't running, the IP resolutions fail.

Other resolutions for non-Microsoft domain sites are fine, and use the DNS
Server as specified for the relevant NIC. XP machines on the network are
also fine.

I'm sure I saw a Microsoft Knowledge Base Article about this behaviour last
week, but I can't find the appropriate search terms to use.

If anyone knows the MS KB Article ID, I would be grateful.

Colin.

"News Group" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> All DNS resolutions for Microsoft websites in the domain microsoft.com eg.
> www.microsoft.com www.support.microsoft.com are directed to the local DNS
> Server. If this DNS Server isn't running, the IP resolutions fail.
>
> Other resolutions for non-Microsoft domain sites are fine, and use the DNS
> Server as specified for the relevant NIC. XP machines on the network are
> also fine.
>
> I'm sure I saw a Microsoft Knowledge Base Article about this behaviour
last
> week, but I can't find the appropriate search terms to use.
>
> If anyone knows the MS KB Article ID, I would be grateful.
>
> Colin.
>
>

Not exactly sure what the issue is. Maybe I missed something obvious?

Are you speaking of forwarding? That is the recommended best practice.
http://support.microsoft.com/?id=300202

Yes, if your internal DNS server on YOUR network fails, then it will be a
problem for everything, especially AD (assuming you're network is AD) and
not just simple INternet access.

Now if that's not it, please be a little more specific so we can better
help.

Thanks

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Thanks for the response Ace.

I'm not talking about Forwarding or any kind of normal DNS configuration
issue (including /etc/hosts). I'm talking about a 'feature' put in Server
2003 which treats Microsoft domain names differently than others.

The issue is that: names in the Microsoft domain are treated differently
than other names ie. there is some sort of extra processing done by either
IE or the OS because the name contains microsoft.com.

The DNS Server that I specify in the Server NIC is ignored, and the
resolution request passed to the local DNS Server.

I don't want the DNS Server that I specify to be ignored.

The MS KB Article (I believe), gave a list of sites within the Microsoft
domain that were treated this way.

Colin

In news:edGdz%(E-Mail Removed),
News Group <(E-Mail Removed)> posted their thoughts, then I
offered mine
> Thanks for the response Ace.
>
> I'm not talking about Forwarding or any kind of normal DNS
> configuration issue (including /etc/hosts). I'm talking about a
> 'feature' put in Server 2003 which treats Microsoft domain names
> differently than others.
>
> The issue is that: names in the Microsoft domain are treated
> differently than other names ie. there is some sort of extra
> processing done by either IE or the OS because the name contains
> microsoft.com.

That I was not aware of. Maybe one of the MS folks can comment on this?

>
> The DNS Server that I specify in the Server NIC is ignored, and the
> resolution request passed to the local DNS Server.

Local DNS server? Which is that? Your DNS server? What DNS server did you
specify, one not in your organization (such as an ISP's)?

Are you listing more than one DNS?
If so, a client machine's DNS resolver service will use whatever DNS
server(s) you specify. If more than one, it uses the first one first. If a
query that goes to the first one cannot be answered by the first one, then
the first one is removed from the eligible resolvers list, then it uses the
next one in line. To make it go back to the first one, you can either
restart the machine, restart the DNS Client service or set a reg key as per
an article that I can post if you need it. It's not a Round Robin or fault
tolerance thing.

>
> I don't want the DNS Server that I specify to be ignored.

It really doesn't ignore it, unless the scenario I described above is being
used.

>
> The MS KB Article (I believe), gave a list of sites within the
> Microsoft domain that were treated this way.

That's one article I would be very interested to read. I would highly
appreciate it if you can post it.

>
> Colin



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Hi Ace,

Thanks for the further reply.

I've simplified matters:

I have a single dual-boot machine.
I have disabled all NIC's bar one.
My (DNS capable) router is specified as the only DNS Server.
When I boot into XP, www.microsoft.com resolves fine.
When I boot into Server 2003, it doesn't.

As you rightly said, once a DNS Server fails it is removed from the list of
eligible Severs. This is where my problem truly lies. I want the Router used
as the Primary DNS, because it is always available. After the Server fails
to reach www.microsoft.com, it will then (unless reset) be using a different
DNS
Server than the client machines (running XP) on the network.

> ...or set a reg key as per an article that I can post if you need it.

I would be grateful if you could send me this article.

> That's one article I would be very interested to read. I would highly
appreciate it if you can post it.

If I wasn't deluding myself and ever find it, I will send you the link.

Colin

In news:(E-Mail Removed),
News Group <(E-Mail Removed)> posted their thoughts, then I
offered mine
> Hi Ace,
>
> Thanks for the further reply.
>
> I've simplified matters:
>
> I have a single dual-boot machine.
> I have disabled all NIC's bar one.
> My (DNS capable) router is specified as the only DNS Server.
> When I boot into XP, www.microsoft.com resolves fine.
> When I boot into Server 2003, it doesn't.
>
> As you rightly said, once a DNS Server fails it is removed from the
> list of eligible Severs. This is where my problem truly lies. I want
> the Router used as the Primary DNS, because it is always available.
> After the Server fails to reach www.microsoft.com, it will then
> (unless reset) be using a different DNS
> Server than the client machines (running XP) on the network.
>
>> ...or set a reg key as per an article that I can post if you need it.
>
> I would be grateful if you could send me this article.
>
>> That's one article I would be very interested to read. I would highly
> appreciate it if you can post it.
>
> If I wasn't deluding myself and ever find it, I will send you the
> link.
>
> Colin

Well, well, well, that is a classic issue with AD if you WANT to use your
router as a DNS address. You are SURELY guaranteeing numerous errors if you
do so. My paycheck is on that one. Reason is AD stores all of it's resource
locations in DNS as SRV (service locator records). If you enlist an external
DNS server (such as an ISP's or your router) you will create numerous
problems because services, DCs, clients, etc, when the want to perform a
directory service function, maybe such as something as simple as loggin in,
it asks DNS where is the DC for my domain, and it fetches that from the
SRVs. If it were to ask the router, can it provide that information?

The recommedation is:
1. Point ALL internal machines to your internal DNS ONLY.
2. Set a forwarder on your internal DNS (in properties, Forwarding tab) to
forward to the ISP. Don't use the router here, otherwise you're introducing
an extra hop, which is a waste).

Make sense?

If you read back thru the many postings in the DNS and AD group, you will
find your configuration is a common configuration error and is problematic
and the responses are pretty much cookie cutters like I posted in how to fix
it. The other groups you posted to wouldn't be able to help out with this
issue.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Thank you Ace.

I'm VERY grateful for the time and trouble you took with my problem.

Many thanks

Colin.

In news:%(E-Mail Removed),
News Group <(E-Mail Removed)> posted their thoughts, then I
offered mine
> Thank you Ace.
>
> I'm VERY grateful for the time and trouble you took with my problem.
>
> Many thanks
>
> Colin.

No problem Colin. I hope it helped out and you get things working.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================