DDNS Working but not 100%

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have setup DDNS in our Enviroment and have a few strange issues.
Current enviroment:
No Active Directory. DNS and DHCP is on same Box. DDNS is enabled and DHCP
server is set to force updates on all clients. DHCP option 015 for DNS
suffix is set on all scopes but not globaly. Machines are a full range of
NT, 9x, 2k, XP Pro.

DDNS is working for our Primary DNS zone on about 50% of our computers.
What I have noticed is that the machines that have a computername of
hostname.dns.suffix.com or a forced DNS suffix in TCP/IP of dns.suffix.com
work fine and work correctly with DDNS. DHCP lists these clients with the
full computername.dns.suffix.com. However, The other clients who have a
computername of "computername." are never updated.
These clients receive DHCP and an issue of Ipconfig /all list the correct
DNS.suffix.com .

Any thoughts why I would have to Force the Suffix on my clients. Shouldn't
DHCP pass this information out with the 015 option?
 
In
Brian Meyer said:
I have setup DDNS in our Enviroment and have a few strange issues.
Current enviroment:
No Active Directory. DNS and DHCP is on same Box. DDNS is enabled
and DHCP server is set to force updates on all clients. DHCP option
015 for DNS suffix is set on all scopes but not globaly. Machines
are a full range of NT, 9x, 2k, XP Pro.

DDNS is working for our Primary DNS zone on about 50% of our
computers. What I have noticed is that the machines that have a
computername of hostname.dns.suffix.com or a forced DNS suffix in
TCP/IP of dns.suffix.com work fine and work correctly with DDNS. DHCP
lists these clients with the full computername.dns.suffix.com.
However, The other clients who have a computername of
"computername." are never updated.
These clients receive DHCP and an issue of Ipconfig /all list the
correct DNS.suffix.com .

Any thoughts why I would have to Force the Suffix on my clients.
Shouldn't DHCP pass this information out with the 015 option?
Click to expand...

Option 015 is a "Connection Specific Suffix" and not the Primary DNS Suffix,
which is what the registration processes uses. There's a difference. With AD
(which you don't have installed yet), there's a GPO setting to configure
this on W2k and newer clients. Otherwise, you'll have to do it manually or
script it. For older clients, that setting goes under TCPIP properties, DNS
tab.

--
Regards,
Ace

G O E A G L E S !!!
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top