Help with DNS over 2 subnets

  • Thread starter Thread starter Dave
  • Start date Start date
D

Dave

Hi,

I want to set up DNS over 2 subnets and don't have any idea on what to do.

Where should I start?

Here are our subnets:
192.168.10.0 / 255.255.255.0 on win2k domain
122.0.0.0 / 255.255.0.0 on NT domain

Are there any articles on how to do this?

Thanks!!!
 
SImple answer is to install DNS on the W2k DNS server and only use that and
have both subnets using the one server. NT4 DNS does not support AD.

Also, if you have another W2k server, you can install it over the NT4
subnet. Create a secondary of the zones on this server and set the Master as
the DC.DNS server in the first subnet.

Curious, why the 122.x.x.x subnet? That's a public IP. Other subnet is
192.168.x.x? Must be a NAT between these subnets. If so, some of this stuff
will just not work without jumping thru hoops (such as creating VPNs, port
remapping, etc). Domain communication going thru a NAT will definitely not
work.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Hi Ace,

I should clarify what I'm tring to do.

What I really want to do is access computers on different subnets with names
instead of IP addresses. I want to do this with a subnet that we have right
now, but eventually I'm gonna want to do it over a VPN to join offices in
different physical locations.

I know the 122.xxx.xxx.xxx is a weird address, but we didn't set that one
up. We have some specialized machines that were set up by a subcontractor
to do a certain job and they set them up on 122.xx. We have a Linksys
broadband router/firewall connecting the 122.xx and 192.xx subnets. The
Linksys is set up as a router and not a firewall.

Anyway, I did a little more research and am beginning to think that WINS
might be the answer to what I need. Am I heading in the right direction?

Thanks!!!!


"Ace Fekay [MVP]"
 
I see.

Yes, if you want NetBIOS name resolution (access by the computer name and
not the FQDN), then WINS is the solution.

I would plan on changing that IP subnet to a different range, such as
192.168.5.0, since your other one is 192.168.10.0, it would seem plausible
to use that instead. It seems that the 122.0.0.0 range is a reserved range
(not sure for what):

OrgName: Internet Assigned Numbers Authority
OrgID: IANA
Address: 4676 Admiralty Way, Suite 330
City: Marina del Rey
StateProv: CA
PostalCode: 90292-6695
Country: US

NetRange: 96.0.0.0 - 126.255.255.255
CIDR: 96.0.0.0/4, 112.0.0.0/5, 120.0.0.0/6, 124.0.0.0/7, 126.0.0.0/8
NetName: RESERVED-8
NetHandle: NET-96-0-0-0-1
Parent:
NetType: IANA Reserved
Comment:
RegDate:
Updated: 2002-09-12


Cheers!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================

Dave said:
Hi Ace,

I should clarify what I'm tring to do.

What I really want to do is access computers on different subnets with names
instead of IP addresses. I want to do this with a subnet that we have right
now, but eventually I'm gonna want to do it over a VPN to join offices in
different physical locations.

I know the 122.xxx.xxx.xxx is a weird address, but we didn't set that one
up. We have some specialized machines that were set up by a subcontractor
to do a certain job and they set them up on 122.xx. We have a Linksys
broadband router/firewall connecting the 122.xx and 192.xx subnets. The
Linksys is set up as a router and not a firewall.

Anyway, I did a little more research and am beginning to think that WINS
might be the answer to what I need. Am I heading in the right direction?

Thanks!!!!


"Ace Fekay [MVP]"
SImple answer is to install DNS on the W2k DNS server and only use that and
have both subnets using the one server. NT4 DNS does not support AD.

Also, if you have another W2k server, you can install it over the NT4
subnet. Create a secondary of the zones on this server and set the
Click to expand...
Master
Click to expand...
 
Thanks!!!

"Ace Fekay [MVP]"
I see.

Yes, if you want NetBIOS name resolution (access by the computer name and
not the FQDN), then WINS is the solution.

I would plan on changing that IP subnet to a different range, such as
192.168.5.0, since your other one is 192.168.10.0, it would seem plausible
to use that instead. It seems that the 122.0.0.0 range is a reserved range
(not sure for what):

OrgName: Internet Assigned Numbers Authority
OrgID: IANA
Address: 4676 Admiralty Way, Suite 330
City: Marina del Rey
StateProv: CA
PostalCode: 90292-6695
Country: US

NetRange: 96.0.0.0 - 126.255.255.255
CIDR: 96.0.0.0/4, 112.0.0.0/5, 120.0.0.0/6, 124.0.0.0/7, 126.0.0.0/8
NetName: RESERVED-8
NetHandle: NET-96-0-0-0-1
Parent:
NetType: IANA Reserved
Comment:
RegDate:
Updated: 2002-09-12


Cheers!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
Click to expand...
 
Back
Top