Converting network addresses with DNS/WINS

  • Thread starter Thread starter Woody
  • Start date Start date
W

Woody

Hello, I am in the middle of having to move a network that
originally had a public class c address used both
internally and externally throughout the network. There
was originally a Primary Domain Server called FB4 that was
a AD/DNS/DHCP/WINS and file and print server with a
206.231.xxx.xxx class c address assigned to it. There was
also a backup domain controller FB10 that AD replicated to
and was a DNS/DHCP/WINS server as well it had an address
of 206.231.xxx.xxx class c address. All of the client
machines are windows 98, 2000 and XP. I have been
migrating all of the internal devices to a new private
class a Addressing scheme behind the firewall. We were
successfull in implementing a new Cisco 6513 Switch
configured layer 2 device to move all of the internal
devices to the switch and assign them dedicated private
10.1.4.1/22 addresses. I took the FB4 and FB10 servers and
assigned them a secondary address of 10.1.4.10 and
10.1.4.11 respectively. I did this to create registered
10. addresses within the DNS Zones. Well the plan was to
have all of the devices reregister themselves to the DNS
servers with the 10. addresses and then once they were all
converted I would remove the 206.231.xxx.xxx address from
the FB4 and FB10 servers leaving the to be at only a 10.
address. Well that was the thought, the problem that I am
having seems to be with WINS resolution. How or what is
the best way to register these devices with WINS as a 10.
addressed device and not the original 260.231.xxx.xxx
address that they originally were? I always thought that
Wins would work with DNS and use DNS to resolve the DNS
and Wins addresses. Is this wrong? Is there a better way
of handling this? What will happen when I attempt to
remove the 206.231.xxx.xxx address from the FB4 and FB10
domain controller servers? How will this affect my
Exchange 2000 server?

Thanks Woody
 
In
Woody said:
Hello, I am in the middle of having to move a network that
originally had a public class c address used both
internally and externally throughout the network. There
was originally a Primary Domain Server called FB4 that was
a AD/DNS/DHCP/WINS and file and print server with a
206.231.xxx.xxx class c address assigned to it. There was
also a backup domain controller FB10 that AD replicated to
and was a DNS/DHCP/WINS server as well it had an address
of 206.231.xxx.xxx class c address. All of the client
machines are windows 98, 2000 and XP. I have been
migrating all of the internal devices to a new private
class a Addressing scheme behind the firewall. We were
successfull in implementing a new Cisco 6513 Switch
configured layer 2 device to move all of the internal
devices to the switch and assign them dedicated private
10.1.4.1/22 addresses. I took the FB4 and FB10 servers and
assigned them a secondary address of 10.1.4.10 and
10.1.4.11 respectively.
Click to expand...

Secondary addresses? You mean additional addresses. Since you are going all
with private IPs, the 10. addresses should be the only ones on all internal
machines, DCs and clients.
I did this to create registered
10. addresses within the DNS Zones. Well the plan was to
have all of the devices reregister themselves to the DNS
servers with the 10. addresses and then once they were all
converted I would remove the 206.231.xxx.xxx address from
the FB4 and FB10 servers leaving the to be at only a 10.
address.
Click to expand...

May as well delete the reverse zone too. Not needed anymore.
You should also run thru all your DNS records, including the NS records
(under the Nameserver tab) to make sure they all have their private IPs.
Remove any references to the old external IPs, or it may cause problems.
Well that was the thought, the problem that I am
having seems to be with WINS resolution. How or what is
the best way to register these devices with WINS as a 10.
addressed device and not the original 260.231.xxx.xxx
address that they originally were?
Click to expand...

As long as you only have the private IP of the WINS servers on all your
machines, they will register into WINS. If they still show the public IP,
the TTL on the records have not expired yet. You can quicken it by deleting
all the records and let them recreate automatically. The next restart on
your machines will register the new IPs. If any static entries, they would
have to changed manually.
I always thought that
Wins would work with DNS and use DNS to resolve the DNS
and Wins addresses. Is this wrong?
Click to expand...

Actually DNS uses WINS, not the other way around, for records it cannot
resolve.
Is there a better way
of handling this? What will happen when I attempt to
remove the 206.231.xxx.xxx address from the FB4 and FB10
domain controller servers?
Click to expand...

I'm surprised they're still in there???
How will this affect my
Exchange 2000 server?
Click to expand...

No problems whatsoever. You're changing the IPs to a private subnet,
correct? As long as all machines internally are only set with the internal
private IPs, everything will work like a charm. If your Exchange server is
receiving mail for your domain, fine, make sure that port 25 is mapped to
the internal private IP of the Exchange server and it will receive mail as
long as the MX record points to an FQDN that resolves to the external NAT
interface's IP.
Thanks Woody
Click to expand...

Also, just an FYI:
Make sure all internal machines ONLY use the internal DNS server. Configure
a forwarder to the ISP under the forwarding tab. If the option is grayed
out, delete the root zone and try again. This article shows both steps:
http://support.microsoft.com/?id=300202

If you are hosting your public domain name, I would suggest to get a
separate server for these public records because mixing public and private
IPs on one MS DNS will definitely cause problems.






--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

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