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

DNS problem

Okay. We have 2 separate Domain controllers for 2 separate companies. 2 different DNS server but only 1 DHCP server to assign IP for both domain since they are on the same VLAN subnet.

I wasn't able to join the PC to the secondary domain because DHCP server was pointing to domain 1 DNS. So i made a new class called NewClass(with the DNS server from domain 2 and did the following command
ipconfig / setclassid "local area network connection" NewClass and it look like i was able to join the domain. But i am still having problem where in the middle to the joining it would error out "seem it it lost connection to the DNS or something. And when i do a ping. It is not getting the DNS from the DNS server from the second company

Huy
0
moonzappa
Asked:
moonzappa
  • 3
  • 2
  • 2
5 Solutions
 
russell124Commented:
I think the best solution here would be to use seperate DHCP servers for each domain, split your subnet range, configure your first DHCP with the split subnet scope, and assign the other half of the subnet to the scope on the second DHCP server.  

With the seperate DHCP servers, you can set different DNS servers for each range.  
0
 
Chris DentPowerShell DeveloperCommented:

Except you'd need reservations for every client in that scenario.

You can't just ensure that name servers on either domain have conditional forwarders for the other domain? Updates will follow the forwarders.

Chris
0
 
Chris DentPowerShell DeveloperCommented:

Hmm no actually, that wouldn't work either unless each DHCP server could forward requests to the other.

There's no way to guarantee which DHCP server will answer a request. That means you either:

1. Assign static IP addresses to all clients (or static DNS entries)
2. Configure each DNS server so it can resolve names in both domains

Chris
0
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.

 
russell124Commented:

Chris, you're right, I wasn't thinking about the ARP broadcasts.   For my solution, the networks would have to be on separate subnets and VLANS.

Otherwise, I think you're going to have to follow go with static IP addresses or set up the DNS resolution as Chris was saying.  
0
 
moonzappaAuthor Commented:
i haven't been able to get a separate subnet going for the new domain yet. I am still working on that
0
 
Chris DentPowerShell DeveloperCommented:

The best thing to do would be to set up DNS so each server can resolve names from both domains. If that's only necessary as a temporary situation then all the better, splitting it off into a separate subnet would make life easier :)

Chris
0
 
moonzappaAuthor Commented:
i guess i should create trust between domain. Since we are almost the same company. Will be accessing same some resources.
What are the necessary steps?
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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