none
DNS Server 2012 R2 - Reverse Lookup Zone IP range RRS feed

  • Question

  • Hi guys,

    we have 255.255.255.192 sunbet mask, this is 64 public IP asresses.
    We have created DMZ zone with subnet mask 255.255.255.224. In new DMZ zone is Public DNS with Windows server 2012 R2. Everything work fine, but we can't create Reverse Lookup Zone. 

    First, we created Reverse Lookup Zone with address 0.xxx.xxx.xx.in-addr.arpa but our provider reject us.
    This is normaly, because we can't have whole class of this IP range.

    OK, we create new Reverse Lookup Zone like this: 64-27.xxx.xxx.xxx.in-addr.arpa.

    Looks OK, but in next step you must create Pointer (PTR).   Here is next trouble, because you can't create that correctly:

    This is just another example with different IP addresses, but same shit for our real example with public IP range:

    Anyone have idea how correctly configure Reverse Lookup Zone?

    Best regards


    Ninja 4 IT



    • Edited by Ninja 4 IT Saturday, September 24, 2016 4:58 AM
    Thursday, September 22, 2016 7:57 PM

All replies

  • Hi,

    According your description,you want to create a delegated subnetted reverse lookup zones.Please check this link for details for both parent and child side for your reference:

    How to configure a subnetted reverse lookup zone on Windows NT, Windows 2000, or Windows Server 2003

    https://support.microsoft.com/en-us/kb/174419


    Best Regards,
    Cartman
    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Friday, September 23, 2016 2:05 AM
  •  

    Thanks for reply, but this is old school theory as like: stop DNS service,  edit in-addr.arpa file  then restart again.  

    I want to hear real experience from users, how is created reverse lookup zone on Win Server 2012.

    Admins who has real experiences know, that creating PTR by  this link (https://support.microsoft.com/en-us/kb/174419) is not possible in Win Server 2012. (picture example in first post).

    Best regards



    Ninja 4 IT


    • Edited by Ninja 4 IT Friday, September 23, 2016 1:42 PM
    Friday, September 23, 2016 1:41 PM
  • Hi,

    Sorry for delay,I have researched for days,and could not find any official document about this behavior,if this issues is a state of emergency for you ,I suggest you open a case with Microsoft, more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.

    Here is the link:

    https://support.microsoft.com/en-us/gp/support-options-for-business


    Best Regards,
    Cartman
    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 4, 2016 1:15 AM
  • Thanks for reply. We bring back reverse lookup zone to our ISP provider. Maybe will be this bug corrected in Windows Server 2016.  I appeal Microsoft, please repair and test this example. 

    Best regards  

    Ninja 4 IT

    Friday, October 21, 2016 11:43 AM
  • does the definitive MS article on subnetting reverse dns zones in the year 2019 still only include information for windows NT, 2000, and 2003?

    https://support.microsoft.com/en-us/help/174419/how-to-configure-a-subnetted-reverse-lookup-zone-on-windows-nt-windows

    Thursday, August 29, 2019 3:57 PM