| Author |
Message |
Patrick
Guest
|
 Posted:
Fri Oct 28, 2005 4:51 pm Post subject:
NT4 --> 2003 Upgrade: How to drop BIND for 2K3 DNS? |
|
|
Hello. We currently use BIND in our environment and are having a hard time
figuring out how to drop it and the timing with changing clients to the new
DNS IP (if we go that route).
Here are the options on the table at this point:
1. Use currently deployed BIND.
1st attempt in lab had unsuccessful AD install, Root DC wasn’t
recognized as AD appends ldap_msdcs to chdmeridian.com (apparent issue).
We can try appending this on the BIND server and upgrading again.
However, a concern is that AD may append this and other conventions
elsewhere causing other issues. Also, BIND implemeantation with AD
may not be as common as AD DNS implementation, leaving us with
with limited online data for research should other issues occur in the
future. This is being looked into.
2. Implement Windows 2003 DNS prior to upgrade.
This would provide DNS that we know to be compatible. However, one
previous test pointing
the AD server being added was also unsuccessful in using 2003 DNS on a
separate server. The cause was not extensively reviewed though.
3. Install DNS on the Root AD server as it being upgraded.
In testing, this has been the most successful thus far. However, the
DNS clients
would need to be pointing to this DNS server either right before the
upgrade or very shortly after. The may be able to use WINs to find
internal PCs, and may be okay finding Internet and internal URLs if
they still pointing to the BIND server, but if they have issues resolving the
Root DC they will not be able to log in.
4. Combination of all three options.
Keep all clients pointing to BIND, Install separate 2003 DNS as a
2ndary to BIND (has all entries in case BIND is failing anywhere), Install
DNS on Root DC as it is upgraded and set as SOA. Clients would point
to BIND initially (as backup and for static IPs), and in DHCP the
DNS would be changed to the new Root DC DNS SOA right after upgrade.
Do you have any other recommendations or is one of these the most feasable?
Thanks in advance! |
|
| Back to top |
|
 |
Wendel Hamilton
Guest
|
| Posted:
Sat Oct 29, 2005 8:50 am Post subject:
RE: NT4 --> 2003 Upgrade: How to drop BIND for 2K3 DNS? |
|
|
Patrick,
I would do it this way (just a suggestion)
Install AD and DNS together.
Set a forwarder in AD to BIND.
Move clients DNS to AD server.
Replicate your domains in BIND to AD.
Remove forwarder to BIND.
Remove BIND.
If you do it this way you can take as long as you like to move domains and
clients from bind.
"Patrick" wrote:
| Quote: | Hello. We currently use BIND in our environment and are having a hard time
figuring out how to drop it and the timing with changing clients to the new
DNS IP (if we go that route).
Here are the options on the table at this point:
1. Use currently deployed BIND.
1st attempt in lab had unsuccessful AD install, Root DC wasn’t
recognized as AD appends ldap_msdcs to chdmeridian.com (apparent issue).
We can try appending this on the BIND server and upgrading again.
However, a concern is that AD may append this and other conventions
elsewhere causing other issues. Also, BIND implemeantation with AD
may not be as common as AD DNS implementation, leaving us with
with limited online data for research should other issues occur in the
future. This is being looked into.
2. Implement Windows 2003 DNS prior to upgrade.
This would provide DNS that we know to be compatible. However, one
previous test pointing
the AD server being added was also unsuccessful in using 2003 DNS on a
separate server. The cause was not extensively reviewed though.
3. Install DNS on the Root AD server as it being upgraded.
In testing, this has been the most successful thus far. However, the
DNS clients
would need to be pointing to this DNS server either right before the
upgrade or very shortly after. The may be able to use WINs to find
internal PCs, and may be okay finding Internet and internal URLs if
they still pointing to the BIND server, but if they have issues resolving the
Root DC they will not be able to log in.
4. Combination of all three options.
Keep all clients pointing to BIND, Install separate 2003 DNS as a
2ndary to BIND (has all entries in case BIND is failing anywhere), Install
DNS on Root DC as it is upgraded and set as SOA. Clients would point
to BIND initially (as backup and for static IPs), and in DHCP the
DNS would be changed to the new Root DC DNS SOA right after upgrade.
Do you have any other recommendations or is one of these the most feasable?
Thanks in advance!
|
|
|
| Back to top |
|
|
Patrick
Guest
|
| Posted:
Sat Oct 29, 2005 8:50 pm Post subject:
RE: NT4 --> 2003 Upgrade: How to drop BIND for 2K3 DNS? |
|
|
Sounds like a good plan, I agree. Thank you!
"Wendel Hamilton" wrote:
| Quote: | Patrick,
I would do it this way (just a suggestion)
Install AD and DNS together.
Set a forwarder in AD to BIND.
Move clients DNS to AD server.
Replicate your domains in BIND to AD.
Remove forwarder to BIND.
Remove BIND.
If you do it this way you can take as long as you like to move domains and
clients from bind.
"Patrick" wrote:
Hello. We currently use BIND in our environment and are having a hard time
figuring out how to drop it and the timing with changing clients to the new
DNS IP (if we go that route).
Here are the options on the table at this point:
1. Use currently deployed BIND.
1st attempt in lab had unsuccessful AD install, Root DC wasn’t
recognized as AD appends ldap_msdcs to chdmeridian.com (apparent issue).
We can try appending this on the BIND server and upgrading again.
However, a concern is that AD may append this and other conventions
elsewhere causing other issues. Also, BIND implemeantation with AD
may not be as common as AD DNS implementation, leaving us with
with limited online data for research should other issues occur in the
future. This is being looked into.
2. Implement Windows 2003 DNS prior to upgrade.
This would provide DNS that we know to be compatible. However, one
previous test pointing
the AD server being added was also unsuccessful in using 2003 DNS on a
separate server. The cause was not extensively reviewed though.
3. Install DNS on the Root AD server as it being upgraded.
In testing, this has been the most successful thus far. However, the
DNS clients
would need to be pointing to this DNS server either right before the
upgrade or very shortly after. The may be able to use WINs to find
internal PCs, and may be okay finding Internet and internal URLs if
they still pointing to the BIND server, but if they have issues resolving the
Root DC they will not be able to log in.
4. Combination of all three options.
Keep all clients pointing to BIND, Install separate 2003 DNS as a
2ndary to BIND (has all entries in case BIND is failing anywhere), Install
DNS on Root DC as it is upgraded and set as SOA. Clients would point
to BIND initially (as backup and for static IPs), and in DHCP the
DNS would be changed to the new Root DC DNS SOA right after upgrade.
Do you have any other recommendations or is one of these the most feasable?
Thanks in advance!
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in