Hi Friends, I am managing a very small network with one router which also acts as the DHCP server. I just configured a DNS server. My network is Windows/Linux mixed environment. All my clients get their IPs from the router (which is a netgear wireless router). I have (or wish to) configured the clients to register themselves on the DNS server as soon as they receive an IP from the DHCP server. All the Linux clients work without any problem. But my Windows 7 client registers only the A record not the PTR. Therefore I can only perform a forward look up but not the reverse look up. But I need this for authentication purposes. I have searched so many threads for a solution. I found mixed answers as listed below: 1. Enabling the PTR registration through the gpedit (I have enabled gpedit->Conputer Configuration->Administrative Templates->Network->DNS Client->DNS Servers, Pimary DNS Suffix, Register DNS records with..., Register OTR Records and Dynamic Update) 2. Configuring the IPv4 properties of the network interface. For this I have set my DNS server as the 'Preferred DNS Server' and in the Advanced->DNS I have selected the options 'Append primary...', Register this connection's address in DNS' and 'Use this connection's DNS suffix in DNS registration' and provided my DNS suffix for the 'DNS suffix for this connection' field. As said above, with these options (even without the gpedit thing) I could only get the forward look up registered. There is not even an attempt for a PTR registration. Can anybody please help? If you need more information in this regard, please let me know. Thanks PS: I have just started configuring Windows 7 for the DNS. I have not tried it on Vista and XP (which I will do in future). Please advise me accordingly.

Hi, Regarding the issue, I suggest using Windows based DHCP server. Also, check if the following KB is helpful. http://support.microsoft.com/kb/816592 Best Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Erm... you do know that the PTR records are created in the Reverse Lookup Zone and not the Forward Zone, right? You did create a proper Reverse Lookup Zone to match your Forward Zone, didn't you?

Hi Niki, Currently I only have the option to use the netgear router. Had I have the option to configure a DHCP server, I would not have had the problem in the first place, as the DHCP server would have taken (or made to take) care to register the records with the DNS server. Hi Bob, I dont completely get your question. As I have mentioned in my initial post, I have my Linux clients registering themselves without any problem. That means that the server is properly configured to get the records from the clients, which also means that I have configured the Linux clients correctly to register themselves to the DNS. If you ask me whether I have properly configured the Windows clients, well, that is my original question; I think I have explained the scenario and what I have done so far and what my problem is. If anything is not clear, please let me know. Thanks guys

Hi, Bob asked if you configured PTR records in the Reverse Lookup Zone correctly. In addition, have you checked KB which I provided? What is your DNS server? If any error is received, please help me collect the screenshot. How to capture a screenshot ------------------------------------------ 1. When the error message occurs, press the Print Screen key (PrtScn) on your keyboard. 2. Click the "Start" menu, type "mspaint" in the Search Bar and Press Enter. 3. In the Paint program, click the "Edit" menu, click "Paste", click the "File" menu, and click "Save". 4. Save the picture onto your desktop and Upload to SkyDrive. Best Regards, NikiPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.