locked
Assignment of IP Addresses RRS feed

  • Question


  • Assignment of IP addresses The DHCP service must be configured on OBELIX (segment B).

    You must ensure that all servers and routers always use the same static addresses and that the addresses do not result in a conflict with other addresses that are dynamically assigned. Consider the creation of a series of exclusions and/or reserved addresses as you see fit.

     Execute the jetpack utility

     Monitor the DHCP server activity logs

     Dynamic addressing for Segment B only .

    Can someone help me with a step by step guide? this is confusing me.

    Thursday, September 14, 2017 6:18 PM

Answers

All replies


  • Assignment of IP addresses The DHCP service must be configured on OBELIX (segment B).

    You must ensure that all servers and routers always use the same static addresses and that the addresses do not result in a conflict with other addresses that are dynamically assigned. Consider the creation of a series of exclusions and/or reserved addresses as you see fit.

     Execute the jetpack utility

     Monitor the DHCP server activity logs

     Dynamic addressing for Segment B only .

    Can someone help me with a step by step guide? this is confusing me.

    Thursday, September 14, 2017 6:22 PM
  • This one may help.

    https://technet.microsoft.com/en-us/library/dd759218(v=ws.11).aspx

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

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

    • Marked as answer by Rob Tracy Thursday, September 14, 2017 6:39 PM
    Thursday, September 14, 2017 6:35 PM
  • Duplicate post.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/7966bc7d-eb32-4300-ae7d-4244497f5f11/assignment-of-ip-addresses?forum=winservermanager

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

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

    Thursday, September 14, 2017 6:36 PM
  • thank you! 
    this is the network diagram for the above process if that gives you a better idea of what needs to be done.
    im doing this all through vBox. 
    Friday, September 15, 2017 3:39 PM
  • Installing the RRAS role on a domain controller will cause you no end to grief and confusion for active directory DNS

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

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

    Friday, September 15, 2017 3:45 PM

  • This requires a dynamic routing solution.

    You must design and deploy a DNS namespace that will be the most appropriate for the company network and supports an external presence (Segment A) and an Active Directory domain (segment B).

    Segment A (www.montreal.org) ( or other appropriate name) The segment A will contain the DNS server IDEFIX and will serve as the external public zone. You must configure IDEFIX as a server that is located in an environment that is potentially at risk and non-secure. Plan and implement a zone that represents the most appropriate solution that will provide the best security under circumstances for this external (public) zone. For obvious reasons, the DNS server must have a primary zone that is file based. You must prevent all information exchange between the two DNS servers. Zone transfer will not be configured or permitted. The minimum number of records that will exist in the primary zone of the DNS server will be created by the administrator as required based on needs. Note: Keep in mind that www.montreal.org must be supported.

    Segment B Implement a zone that represents the most appropriate that will allow for the best possible security for the internal zone (Active Directory). Configure the Active Directory domain as described in the previous section. The records in this zone will be dynamically created. It is imperative that the users that are part of this domain (Members of the Active Directory) be able to obtain a name resolution from both of the DNS servers. The users of this zone must also be able to access the site www.montreal.org.

    Note : The DNS implementation requires a contiguous namespace Ensure that the appropriate dynamic records exist on OBELIX SOA for OBELIX NS for OBELIX A for OBELIX A for ASTERIX A for CLIENTDOM1

     
    Monday, September 18, 2017 5:21 PM