[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 427
  • Last Modified:

DNS server Windows 2003 R2

Hi Experts,

We have two networks. and We have DNS functioning fine on the 192 subnet, but no DNS on the 10 subnet. I think this is causing us authentication/logon issues because more often then not I get a "Windows cannot contact a logon server to authenticate" blah blah...

What I'm thinking to resolve the logon server is to create an independant DNS server on the 10 side (The DC for the 10 side has a NIC in both networks). What I DON"T want to do, is replicate or (and this is the key) have internet access. There is to be no name resolution on the 192 side of the network.

This is running W2k3 R2 x64 if this helps. I have just installed the DNS role but I'm not sure how best to configure DNS to prevent replication or internet access.
There is no DHCP either (and is required to remain static)

At the moment and DNS resolution that is needed is on client side hosts files (there is only 9 clients, 2 servers on this network)
Tim Palmer
Tim Palmer
  • 2
1 Solution
Suliman Abu KharroubIT Consultant Commented:
To prevent internet names resolution, create a new zone in the new dns server name ".".
Tim PalmerLevel 3 Escalation TechAuthor Commented:
Never mind, the issue was with AD Sites and Services.
Tim PalmerLevel 3 Escalation TechAuthor Commented:
The issue was unrelated to DNS

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now