Dear all Server 2003 Sp2 (AD, DHCP, DNS) I have a DHCP server with the following range 192.168.0.1 - 192.168.1.254. The DHCP updates both the DNS A and PTR Records for the range 192.168.0.1 - 192.168.0.254 but DHCP is not updating PTR Records for range 192.168.1.0 - 192.168.1.254 it does update the A record on DNS and update DHCP list if the IP is dynamic. And if I assign a static IP computer on this range (192.168.1.1 – 192.168.1.254) lets say if I put a static IP 192.168.1.101 on a computer it does not get updated on DHCP (means DHCP list didn’t get that IP at all) so DHCP does not update the A record on the DNS but if I issue ipconfig /flushdns and RegisterDns command from the static IP computer it does update the A record on the DNS but DHCP list still didn’t recognised the IP. "The Security System could not establish a secured connection with the server DNS/xxxx.xxx.xxx. No authentication protocol was available". This is the only message I have found on event viewer on both computers and the DNS server does not have any error message on the Event Viewer, I am really confused and any help will be really appreciated

When you assign static ip to a workstation you bypass dhcp server completely. DHCP server has nothing to do with a static ip entry and as such can't update DNS. You have to do that MANUALLY with a static ip in DNS. The registerdns command is just that, register in dns, nothing more. ONLY if the ip is provided by dhcp [dynamic] will it register in DNS. edited by moderator

Thank you very much wanderer, it clears every thing in my mind, just one more question why do the DHCP does not update the PTR record on DNS for 192.168.1.0 range even when its a dynamic lease. there is a computer icon with pencil (which abvoiusly means that the address will not be leased out). If I assign a static IP on 192.168.0.1 range the A record and PTR updates automatically and on 192.168.1.0 range i have to update the record manually or run the RegDNS command. If you can put some light on this I really appreciate that And by mistake i clicked on votes when it was on negative i was trying to do it opposite and was increasing the number

x.x.1.x and x.x.0.x are two different subnets. Sounds like you are trying to do a superscope with x.x.0.x and x.x.1.x. What is the submask you are using? Have you reviewed these steps? http://technet.microsoft.com/en-us/...

I have setup my scope as follow One Scope Start IP - 192.168.0.1 End IP - 192.168.1.254 Subnet mask is 255.255.254.0 My both subnets can access internet, the only problem is that my second subnet is not registering PTR Records. I will check the link and will post back. Thnak you once again

I have read the DHCP article, it mentioned the superscope and multiscope does not mention the scope option I have, for superscope the subnetmask should be 255.255.255.0 for both subnets and I only created one scope with subnet 255.255.254.0 and the range 192.168.0.1 to 192.168.1.254

255.255.254.0 is the superscope subnet mask for 192.168.0.0-192.168.1.255 http://technet.microsoft.com/en-us/... says: "Before you create a superscope, you must use the DHCP MMC snap-in to define at least one scope to be included in the superscope. Scopes added to a superscope are called member scopes. You can add additional member scopes either from the superscope menu, or from the individual scope menus." You don't mention member scopes so I have to wonder if you followed this procedure.