dns suffix?

  • Thread starter Thread starter g
  • Start date Start date
G

g

Hello, I have a windows nt 4 network that I want to upgrade to windows
2000 ad.
My dhcp server is on a windows nt 4 server.
I would like to prepare my site for ad before doing the upgrades. I put on
a dynamic dns server (allow dynamic updates) and pointed a subnet to it.
All my clients are windows 2000.

The problem is, even if i put 015 as my new dns name the client suffix
does not get updated after a reboot or even two. I have to manually go and
add it to the network identification in system and then reboot. Then and
only then do the clients update there a records.

What am i doing wrong?

Thanks.
 
In
g said:
Hello, I have a windows nt 4 network that I want to upgrade to windows
2000 ad.
My dhcp server is on a windows nt 4 server.
I would like to prepare my site for ad before doing the upgrades. I
put on a dynamic dns server (allow dynamic updates) and pointed a
subnet to it. All my clients are windows 2000.

The problem is, even if i put 015 as my new dns name the client suffix
does not get updated after a reboot or even two. I have to manually
go and add it to the network identification in system and then
reboot. Then and only then do the clients update there a records.

What am i doing wrong?

Thanks.
Click to expand...

One missing bit of information, what OS is the DNS server?
Also, I am not sure if NT4 DHCP supports option 81 for DNS updates, someone
else might answer that one.
 
In
Kevin D. Goodknecht said:
In

One missing bit of information, what OS is the DNS server?
Also, I am not sure if NT4 DHCP supports option 81 for DNS updates,
someone else might answer that one.
Click to expand...

No, NT4 DHCP doesn't support DDNS Option 081.

In this case, the supporting background services is recommended to be
updated to W2k3 (DNS, DHCP, WINS, etc) prior to an upgrade.
--
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
 
One missing bit of information, what OS is the DNS server?
Also, I am not sure if NT4 DHCP supports option 81 for DNS updates, someone
else might answer that one.
Click to expand...

Hi
the dns servers are windows 2000 member servers atm.
the dhcp server is nt4
Ah so 015 does not update the client suffix? just the search domain?
 
No, NT4 DHCP doesn't support DDNS Option 081.

In this case, the supporting background services is recommended to be
updated to W2k3 (DNS, DHCP, WINS, etc) prior to an upgrade.
Click to expand...

Hi thanks for the reply
As far as i am aware option 081 is so that dhcp servers update dns records
for clients that are unable or are set not to do ddns. I do not want this.
I want the dhcp server to change the dns suffix on the client, so intead
of it being computer1 in network identification it is
computer1.mydomain.com.
 
In
g said:
Hi
the dns servers are windows 2000 member servers atm.
the dhcp server is nt4
Ah so 015 does not update the client suffix? just the search domain?
Click to expand...

Oh! That was the question, it is for giving the DHCP client a domain suffix,
there is no installed option for giving clients a search list by DHCP
It will only publish the connection specific DNS suffix.
 
In
g said:
Hi thanks for the reply
As far as i am aware option 081 is so that dhcp servers update dns
records for clients that are unable or are set not to do ddns. I do
not want this. I want the dhcp server to change the dns suffix on the
client, so intead of it being computer1 in network identification it
is computer1.mydomain.com.
Click to expand...

Kevin answered your question on this.

You'll have to either set it manually, or when you join a domain and the
checkbox is checked to change suffix with membership changes or set it with
a GPO. But since you have an NT4 domain, the latter will not work for you.


--
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
 
This DHCP option only gives the client machine a connection specific DNS suffix. If the option isn't checked to use the
conenction specific DNS suffix in DNS registration, then the client will use the primary DNS suffix. The primary DNS suffix should
change to that of the AD domain once the client is made a member of that domain.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
Kevin answered your question on this.
Click to expand...

No actually he didnt, he suggested a work around, for which I thank him.

My question was:

The problem is, even if i put 015 as my new dns name the client suffix
does not get updated after a reboot or even two. I have to manually
go and add it to the network identification in system and then
reboot. Then and only then do the clients update there a records.
Click to expand...

Kevin suggested that I used a ddns capable dhcp server to update my client
records for my clients. I asked how to get my clients to update
themselves. I apparently have to go around to each client and add the dns
suffix in, and then reboot. Yay ad.

Thanks
 
In
g said:
No actually he didnt, he suggested a work around, for which I thank
him.

My question was:

The problem is, even if i put 015 as my new dns name the client suffix

Kevin suggested that I used a ddns capable dhcp server to update my
client records for my clients. I asked how to get my clients to update
themselves. I apparently have to go around to each client and add the
dns suffix in, and then reboot. Yay ad.

Thanks
Click to expand...

Your question was very unclear as to what you are trying to achieve. DHCP
will not add the suffix to the network identification it will add it to the
ipconfig and if you have DDNS capable DHCP and DNS it will register in the
zone for option 015. It won't change the NIC GUI if the client is DHCP
enabled if you type ipconfig /release ipconfig /renew then type ipconfig
/all it will show the connection specific suffix for you.

The network ID is given when you join a domain or workgroup.
 
Your question was very unclear as to what you are trying to achieve.
Click to expand...

Ah ok, sorry.

Nt4 domain
nt4 dhcp server
windows 2000 dns server dynamic updates allowed
clients have no dns suffix in network identification
clients are already part of a windows nt4 domain

When I switch them to a ddns server they do not update their a records in
the dns file.
If I manually add the dns suffix in network identification it does add
itself.

I would like to go to windows 2000 ad, but I am trying to minimize the
downtime/problems/changes, so I would like to get as much as possible
working before I upgrade and change my settings.

If I change to windows 2000 dhcp server can i supply a dns suffix to each
computer in the network identification, I am not talking about a network
suffix.

If I upgrade to a windows 2000 ad using the same downlevel domain, and a
proper dns structure will my clients add this dns suffix in the network
identification if they have the change dns suffix when changing domain
ticked off.

Question:
The network ID is given when you join a domain or workgroup.

Are you talking about a windows 2000 ad domain, windows nt4 domain or a dns domain? Because they are
different things.


Sorry but I really need to figure this out before I go any further,
walkign around to all my clients is going to take a heck of a long time.
running a reg patch and rebooting them will still be a problem.

thanks
 
In
g said:
Ah ok, sorry.

Nt4 domain
nt4 dhcp server
windows 2000 dns server dynamic updates allowed
clients have no dns suffix in network identification
clients are already part of a windows nt4 domain

When I switch them to a ddns server they do not update their a
records in
the dns file.
Click to expand...

You are using NT4 DHCP I'm not sure how that handles registration, or if it
does. HT4 was way long time ago for me and I did not use DHCP on NT4. If you
would move DHCP to Win2k I'm sure it will work.
If I manually add the dns suffix in network identification it does add
itself.
Click to expand...
Yes it will, but DHCP will not add the DNS Suffix to the computer ID, not
even Win2k will do that, it will add the suffix to the connection suffix.
And Win2k DHCP will register the computer host name in the zone for the
suffix in option 015.
I would like to go to windows 2000 ad, but I am trying to minimize the
downtime/problems/changes, so I would like to get as much as possible
working before I upgrade and change my settings.
Click to expand...

I understand what you are saying, if you are going to start from an upgrade
of your NT4 PDC you should have few problems if you keep the same NetBIOS
name *before* you upgrade the PDC to Win2k in its TCP/IP properties make
sure the Domain suffix matches the DNS name of what your Win2k DNS name will
be or it will cause a disjointed namespace.
If I change to windows 2000 dhcp server can i supply a dns suffix to
each
computer in the network identification, I am not talking about a
network
suffix.
Click to expand...

The network ID will not change until its domain name is changed I wish I
could tell you somethinng better but you are going to have to visit each
workstation to do that. It will only take a few minutes so long as they are
all using the local DNS address only.
If I upgrade to a windows 2000 ad using the same downlevel domain,
and a
proper dns structure will my clients add this dns suffix in the
network
identification if they have the change dns suffix when changing domain
ticked off.

Question:
The network ID is given when you join a domain or workgroup.

Are you talking about a windows 2000 ad domain, windows nt4 domain or
a dns domain? Because they are different things.
Click to expand...

If you change the ID of your computers while on an NT4 domain NT4 wil no
longer recognise the computer name as a member.
I think you are trying to put the buggy in front of the horse.

I think you will have few problems if you choose your name wisely, so long
as you cover all the bases on the DC first.
 
In

You are using NT4 DHCP I'm not sure how that handles registration, or if it
does. HT4 was way long time ago for me and I did not use DHCP on NT4. If you
would move DHCP to Win2k I'm sure it will work.

Yes it will, but DHCP will not add the DNS Suffix to the computer ID, not
even Win2k will do that, it will add the suffix to the connection suffix.
And Win2k DHCP will register the computer host name in the zone for the
suffix in option 015.


I understand what you are saying, if you are going to start from an upgrade
of your NT4 PDC you should have few problems if you keep the same NetBIOS
name *before* you upgrade the PDC to Win2k in its TCP/IP properties make
sure the Domain suffix matches the DNS name of what your Win2k DNS name will
be or it will cause a disjointed namespace.


The network ID will not change until its domain name is changed I wish I
could tell you somethinng better but you are going to have to visit each
workstation to do that. It will only take a few minutes so long as they are
all using the local DNS address only.


If you change the ID of your computers while on an NT4 domain NT4 wil no
longer recognise the computer name as a member.
I think you are trying to put the buggy in front of the horse.

I think you will have few problems if you choose your name wisely, so long
as you cover all the bases on the DC first.
Click to expand...

Thanks, I really appreciate your time and input, guess I will just have to
go around :P
thanks again
 
Try this and see if it helps:
JSI Tip 5470. Freeware utility adds or removes DNS suffixes from remote
computers:
http://www.jsiinc.com/subk/tip5400/rh5470.htm

--
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