Dynamic DNS update problem

  • Thread starter Thread starter Blake
  • Start date Start date
B

Blake

We have Win2k3 DHCP/DNS server, non-AD integrated zone that is configured to
allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But many
machines list 'host.' (without the domain name) and, of course, won't
process DDNS updates correctly. I believe these machines are XP machines
and I thought I had a KB article a couple years back about dynamic DNS
updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it doesn't
work for all clients.

Any ideas?

Blake
 
Blake said:
We have Win2k3 DHCP/DNS server, non-AD integrated zone that is configured
to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But many
machines list 'host.' (without the domain name) and, of course, won't
process DDNS updates correctly. I believe these machines are XP machines
and I thought I had a KB article a couple years back about dynamic DNS
updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it doesn't
work for all clients.

Clients should ALSO be set on their SYSTEM control
panel to have the correct DNS name (computer name
suffix).

Note this is the name of the computer in the SYSTEM
control panel not on the NIC properties.
 
I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

Blake

Herb Martin said:
Blake said:
We have Win2k3 DHCP/DNS server, non-AD integrated zone that is configured
to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But many
machines list 'host.' (without the domain name) and, of course, won't
process DDNS updates correctly. I believe these machines are XP machines
and I thought I had a KB article a couple years back about dynamic DNS
updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it doesn't
work for all clients.

Clients should ALSO be set on their SYSTEM control
panel to have the correct DNS name (computer name
suffix).

Note this is the name of the computer in the SYSTEM
control panel not on the NIC properties.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Blake said:
We have Win2k3 DHCP/DNS server, non-AD integrated zone that is configured
to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But many
machines list 'host.' (without the domain name) and, of course, won't
process DDNS updates correctly. I believe these machines are XP machines
and I thought I had a KB article a couple years back about dynamic DNS
updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it doesn't
work for all clients.

Any ideas?

Blake
 
Blake said:
I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

No, the System Control panel should be set IN ADDITION
to the DHCP settings.

It really should be set when the computer is joined to the
domain (or before even when the computer is installed.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Blake said:
I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

Blake

Herb Martin said:
Blake said:
We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are XP
machines and I thought I had a KB article a couple years back about
dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Clients should ALSO be set on their SYSTEM control
panel to have the correct DNS name (computer name
suffix).

Note this is the name of the computer in the SYSTEM
control panel not on the NIC properties.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Blake said:
We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are XP
machines and I thought I had a KB article a couple years back about
dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Any ideas?

Blake
 
that's what I figured - these machines aren't controlled by us (they are
student-owned computers)

I was hoping that all the DDNS issues could be cleared up via DHCP

Thanks!

Blake

Herb Martin said:
Blake said:
I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

No, the System Control panel should be set IN ADDITION
to the DHCP settings.

It really should be set when the computer is joined to the
domain (or before even when the computer is installed.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Blake said:
I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

Blake

Herb Martin said:
We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are XP
machines and I thought I had a KB article a couple years back about
dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Clients should ALSO be set on their SYSTEM control
panel to have the correct DNS name (computer name
suffix).

Note this is the name of the computer in the SYSTEM
control panel not on the NIC properties.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are XP
machines and I thought I had a KB article a couple years back about
dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Any ideas?

Blake
 
Blake said:
that's what I figured - these machines aren't controlled by us (they are
student-owned computers)

I was hoping that all the DDNS issues could be cleared up via DHCP

What's the purpose of registering them in DNS?

(Seriously, because the answer matters to the recommendations)

If it is so the user can SHARE their drives there are two outs:

1) Use WINS/NetBIOS which typically just works anyway

2) Tell them they must set their machine for this feature to work

If it is for something else we can work through that, but "client"
machines don't always NEED to be registered, do they?

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Thanks!

Blake

Herb Martin said:
Blake said:
I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

No, the System Control panel should be set IN ADDITION
to the DHCP settings.

It really should be set when the computer is joined to the
domain (or before even when the computer is installed.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Blake said:
I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

Blake

We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are XP
machines and I thought I had a KB article a couple years back about
dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Clients should ALSO be set on their SYSTEM control
panel to have the correct DNS name (computer name
suffix).

Note this is the name of the computer in the SYSTEM
control panel not on the NIC properties.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are XP
machines and I thought I had a KB article a couple years back about
dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Any ideas?

Blake
 
We have some who run server type services (mainly web servers) and want
standard name -> IP resolution. It isn't a big deal (normally those savy
enough to run web servers can configure their machines correctly)

Thanks!

Blake

Herb Martin said:
Blake said:
that's what I figured - these machines aren't controlled by us (they are
student-owned computers)

I was hoping that all the DDNS issues could be cleared up via DHCP

What's the purpose of registering them in DNS?

(Seriously, because the answer matters to the recommendations)

If it is so the user can SHARE their drives there are two outs:

1) Use WINS/NetBIOS which typically just works anyway

2) Tell them they must set their machine for this feature to work

If it is for something else we can work through that, but "client"
machines don't always NEED to be registered, do they?

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Thanks!

Blake

Herb Martin said:
I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

No, the System Control panel should be set IN ADDITION
to the DHCP settings.

It really should be set when the computer is joined to the
domain (or before even when the computer is installed.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

Blake

We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are
XP machines and I thought I had a KB article a couple years back
about dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Clients should ALSO be set on their SYSTEM control
panel to have the correct DNS name (computer name
suffix).

Note this is the name of the computer in the SYSTEM
control panel not on the NIC properties.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are
XP machines and I thought I had a KB article a couple years back
about dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Any ideas?

Blake
 
Blake said:
We have some who run server type services (mainly web servers) and want
standard name -> IP resolution. It isn't a big deal (normally those savy
enough to run web servers can configure their machines correctly)

That is sort of where I was going. Those who have the
need can be expective to follow the instructions.

Also, you SHOULD be able to use IE (specifically) to
access NetBIOS named web sites, e.g.,:

http://NetbiosServerName/

Note: This is NOT (necessarily) taking advantage of the
DNS suffix but rather directly resolving through NetBIOS
(which is a feature of IE and perhaps not of other browsers.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Thanks!

Blake

Herb Martin said:
Blake said:
that's what I figured - these machines aren't controlled by us (they are
student-owned computers)

I was hoping that all the DDNS issues could be cleared up via DHCP

What's the purpose of registering them in DNS?

(Seriously, because the answer matters to the recommendations)

If it is so the user can SHARE their drives there are two outs:

1) Use WINS/NetBIOS which typically just works anyway

2) Tell them they must set their machine for this feature to work

If it is for something else we can work through that, but "client"
machines don't always NEED to be registered, do they?

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
Thanks!

Blake

I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

No, the System Control panel should be set IN ADDITION
to the DHCP settings.

It really should be set when the computer is joined to the
domain (or before even when the computer is installed.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

I'll check that, Herb.

I imagine that can't be configured via DHCP, huh?

Blake

We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are
XP machines and I thought I had a KB article a couple years back
about dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Clients should ALSO be set on their SYSTEM control
panel to have the correct DNS name (computer name
suffix).

Note this is the name of the computer in the SYSTEM
control panel not on the NIC properties.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

We have Win2k3 DHCP/DNS server, non-AD integrated zone that is
configured to allow dynamic updates.

In the DHCP MMC under 'leases' many of the machines are listed as
'host.subdomain.domain.tld' and these work fine regarding DDNS. But
many machines list 'host.' (without the domain name) and, of course,
won't process DDNS updates correctly. I believe these machines are
XP machines and I thought I had a KB article a couple years back
about dynamic DNS updates on XP - but can't find it.

I am setting the DNS suffix via option 015 in DHCP server, but it
doesn't work for all clients.

Any ideas?

Blake
 
Back
Top