Switch provided DHCP not registering in DNS

[insureme]

I've got a main hub with fifteen branches, and I'm finding that the devices that are receiving DHCP from the network devices are not registered in DNS. Can anyone tell me how I might fix this. DC's are Win2K3. Thanks.

 

[burtsbees]

You're posting this in the Cisco Switches forum because...the switches are providing DHCP? If so, what model?

Burt

 

[insureme]

I'm sorry it looks like i hit the wrong link. i think these devices are 2800 and 1700 routers, I don't have access to everything here yet. i wasn't left much to work with.

 

[ADB100]

The subnets probably aren't configured on the DNS server (reverse lookup zones). There are no DHCP options that would tell a client not to register with DNS (assuming Windows 2000 or later clients). Check if the subnets for each of the remote sites are in the reverse lookup zones and have the appropriate settings.

The correct DNS servers are being provided aren't they?

Andy

 

[wabob]

Do you have the "import all" parameter in the ip dhcp pool on the switch?

 

[insureme]

so now I'm wondering if what I'm seeing is just normal. the only devices (after closer inspection) are the thin clients. do thin clients normally register with DNS? I've got printers, and other DHCP devices that i see are registered. I looked at the Thin clients config but found nowhere to specifically tell it to register with DNS like you can do in windows, but the DNS servers are configured. i realize this has gone off-topic.

 

[ADB100]

This sounds like the DNS updating service provided by Windows 2000/2003 DHCP. If you open up the Windows 2000/2003 DHCP manager, right-click one of the servers or a specific scope and click properties, one of the tabs is 'DNS'. From here you can make the DHCP server automatically update DNS for clients that don't support dynamic DNS registration (such as Windows 98, printers etc).

And yes, this has gone off topic )

Andy