Resolving non published domain names

  • Thread starter Thread starter dylan.ebner
  • Start date Start date
D

dylan.ebner

Here is my problem. My comany has a windows 2000 Domain controller that
is also the DNS server. The domain is smapledomain.com. We have a vpn
connection to another company that we pull a web based application. The
problem is the application uses http statements like app.companyb.com.
The problem is app.companyb.com will not resolve on our network because
it is not a published domain name. Is it possible to get these domains
to resolve without having to add entries the each computers host file?
I have tried adding a new zone to my domain controller called
companyb.com and then adding the appropriate entries. This works for
what I add. But then when I try to resolve things like www.companyb.com
I get no entry found. I tried delegateing *.companyb.com to an
authorative name server but that didn't work.

Any ideas???
 
Here is my problem. My comany has a windows 2000 Domain controller that
is also the DNS server. The domain is smapledomain.com. We have a vpn
connection to another company that we pull a web based application. The
problem is the application uses http statements like app.companyb.com.
The problem is app.companyb.com will not resolve on our network because
it is not a published domain name. Is it possible to get these domains
to resolve without having to add entries the each computers host file?
I have tried adding a new zone to my domain controller called
companyb.com and then adding the appropriate entries. This works for
what I add. But then when I try to resolve things like www.companyb.com
I get no entry found. I tried delegateing *.companyb.com to an
authorative name server but that didn't work.
Click to expand...

You must add www as a host in the companyb.com zone.

/Per W.
 
Back
Top