themightydude
asked on
forwarding dns for separate domain
Quick question...trying to wrap my head around this but having a hard time.
We have a company that is abc.com
They have their own domain / network / active directory etc etc.
Now this company has started a second company which will be in the same building and on the same network, but they want a separate domain for this company, but they want the users to be on the same network as everyone else.
So what I did, was created a separate network for the server.
Users and servers for abc.com are on a 172.x.x.x network and the xyz.com server is on a 10.100.x.x network.
I can ping that xyz.com server by IP just fine from the 172 network and can ping from that server to the 172 network. However I can't add a computer to the domain, because it is a different domain and the DHCP servers only deliver DNS Info for the DNS servers for company abc.com.
Now, if I make the primary DNS on one of the computers the IP for the xyz.com dns/domain controller I can add that computer to the domain just fine. But adding the xyz.com dns/domain controller as a third DNS server to client computers does not work..only when it is a primary DNS.
So I guess my question is, how can I make users who sit on abc.com network be able to talk to the XYZ.com domain controller without having to manually assign a primary DNS server?
Hopefully that makes sense.
We have a company that is abc.com
They have their own domain / network / active directory etc etc.
Now this company has started a second company which will be in the same building and on the same network, but they want a separate domain for this company, but they want the users to be on the same network as everyone else.
So what I did, was created a separate network for the server.
Users and servers for abc.com are on a 172.x.x.x network and the xyz.com server is on a 10.100.x.x network.
I can ping that xyz.com server by IP just fine from the 172 network and can ping from that server to the 172 network. However I can't add a computer to the domain, because it is a different domain and the DHCP servers only deliver DNS Info for the DNS servers for company abc.com.
Now, if I make the primary DNS on one of the computers the IP for the xyz.com dns/domain controller I can add that computer to the domain just fine. But adding the xyz.com dns/domain controller as a third DNS server to client computers does not work..only when it is a primary DNS.
So I guess my question is, how can I make users who sit on abc.com network be able to talk to the XYZ.com domain controller without having to manually assign a primary DNS server?
Hopefully that makes sense.
ASKER
But that won't resolve the issue of the not being able to join that domain since it is a seperate domain right?
We just separated IP's for sake of keeping them somewhat separate.
We just separated IP's for sake of keeping them somewhat separate.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cool..ok I think that will do what I need.
I created a stub zone on the 2003 DNS server to add records from the new server which is 2008 server R2..however I don't see where to configure zone transfer options on the 2008 R2 box? I clicked the domain in DNS and hit properties, but don't see a "zone transfer" tab.
Any ideas where that might be?
I created a stub zone on the 2003 DNS server to add records from the new server which is 2008 server R2..however I don't see where to configure zone transfer options on the 2008 R2 box? I clicked the domain in DNS and hit properties, but don't see a "zone transfer" tab.
Any ideas where that might be?
ASKER
Nevermind..I"m a idiot..found the zone transfer part.
You don't have to do Zone transfers with stub zones.
ASKER
Hmm..well when i create the stub zone on the abc.com domain, it says it couldn't load the zone information from the xyz.com domain.
ASKER
Ok scratch that...the data transferred and I can ping xzyz.com from abc.com's network.
However if I try to ping a server on xyz.com it won't work.
the domain/dns controller is gb.local @ 10.100.1.5.
I can ping gb.local and get a response from that IP.
But the server name is GB-FS1..if I ping GB-FS1 I don't get a ping response.
However if I try to ping a server on xyz.com it won't work.
the domain/dns controller is gb.local @ 10.100.1.5.
I can ping gb.local and get a response from that IP.
But the server name is GB-FS1..if I ping GB-FS1 I don't get a ping response.
Run ipconfig /flushdns on the servers that can't ping using names.
ASKER
Did that and not working..
ipconfig /flushdns on the gb-fs1 server
and
ipconfig /flushdns on my laptop
Get a cannot find host gb-fs1.
There is an A entry in the DNS server for that name though, so it seems like it should work.
ipconfig /flushdns on the gb-fs1 server
and
ipconfig /flushdns on my laptop
Get a cannot find host gb-fs1.
There is an A entry in the DNS server for that name though, so it seems like it should work.
ASKER
Ok..actually, I can ping it by doing:
ping gb-fs1.gb.local
Is that how we will have to access the server?
ping gb-fs1.gb.local
Is that how we will have to access the server?
ASKER
actually scratch all that...I'm a idiot.
I'm on a different domain, so it makes sense that I have to to gb-fs1.gb.local in order to access that server.
At least I think it does...lol
I'm on a different domain, so it makes sense that I have to to gb-fs1.gb.local in order to access that server.
At least I think it does...lol
Yeah. You have to use the full FQDN to access stuff in the other domain. You can modify the DNS settings to add the other domain to the DNS append list, though.
domain1 -> 192.1.1.1
domain2 -> 192.1.1.1
you shouldnt have them on seperate ips