Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > Browsing Microsoft Websites on a Server 2003 Domain Controller
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 3rd April 12:01
news group
External User
 
Posts: 1
Default Browsing Microsoft Websites on a Server 2003 Domain Controller



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, http://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 http://www.microsoft.com, it will then (unless reset) be using a different
DNS
Server than the client machines (running XP) on the network.

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


appreciate it if you can post it.

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

Colin
  Reply With Quote


  sponsored links


2 3rd April 12:02
ace fekay [mvp]
External User
 
Posts: 1
Default Browsing Microsoft Websites on a Server 2003 Domain Controller



In news:uhFHZvyuDHA.1596@TK2MSFTNGP10.phx.gbl,
News Group <news.paradoxa@btopenworld.com> posted their thoughts, then I
offered mine

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
--
=================================
  Reply With Quote
3 3rd April 12:02
news group
External User
 
Posts: 1
Default Browsing Microsoft Websites on a Server 2003 Domain Controller


Thank you Ace.

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

Many thanks

Colin.
  Reply With Quote
4 3rd April 12:02
ace fekay [mvp]
External User
 
Posts: 1
Default Browsing Microsoft Websites on a Server 2003 Domain Controller


In news:%237xNEeCvDHA.1756@TK2MSFTNGP09.phx.gbl,
News Group <news.paradoxa@btopenworld.com> posted their thoughts, then I
offered mine


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
--
=================================
  Reply With Quote
Reply


Thread Tools
Display Modes




Copyright © 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666