none
DNS and DHCP on Dynamic Linksys Router

    Question

  • I am setting up a 2003 AD server and the IP of the router is not static to the best of my knowledge. I would like to join the computers to the domain and allow them to access both the internal network, and the internet. This is my configuration. 

    1. 2003 Standard Edition IP - 192.168.1.10(Static IP), 255.255.255.0(Subnet), 192.168.1.1(Gateway), 192.168.1.10 (DNS).

    2. Services - AD, DHCP, DNS 

    3. Router Configuration - 192.168.1.1 (LAN), 24.206.37.88 (WAN), 24.25.5.61 (Provider DNS), 24.25.5.60 (Provider DNS2)

     

    How do you recommend I setup DNS, and DHCP from a fresh install to accomplish my goal?

     

    Thanks!

     

    Thursday, June 16, 2011 1:48 PM

Answers

  • So, the most simple way is to set up DHCP server with scope 192.168.1.0/24 (choose pool yourslef i.e. 192.168.1.50 - 192.168.1.90; depends on your needs) with options:

    003 (Router;Default Gateway) 192.168.1.1

    006 (DNS servers list) -> IP address of your DC 192.168.1.10

    015 -> Full DNS Domain Name (FQDN) i.e. testenv.local

    then on your DC (which has DNS) configure in Forwarders section IP address of your ISP DNS server with IP 24.25.5.61 and 24.25.5.60

    How to do that, you will find in this MS article at

    http://technet.microsoft.com/en-us/library/cc787071(WS.10).aspx

    but remember that DHCP scope configuration should have ONLY internal DNS servers (in this case only DC)


    Regards, Krzysztof


    • Marked as answer by Tiger Li Friday, June 17, 2011 3:12 AM
    Thursday, June 16, 2011 2:42 PM

All replies

  • So, the most simple way is to set up DHCP server with scope 192.168.1.0/24 (choose pool yourslef i.e. 192.168.1.50 - 192.168.1.90; depends on your needs) with options:

    003 (Router;Default Gateway) 192.168.1.1

    006 (DNS servers list) -> IP address of your DC 192.168.1.10

    015 -> Full DNS Domain Name (FQDN) i.e. testenv.local

    then on your DC (which has DNS) configure in Forwarders section IP address of your ISP DNS server with IP 24.25.5.61 and 24.25.5.60

    How to do that, you will find in this MS article at

    http://technet.microsoft.com/en-us/library/cc787071(WS.10).aspx

    but remember that DHCP scope configuration should have ONLY internal DNS servers (in this case only DC)


    Regards, Krzysztof


    • Marked as answer by Tiger Li Friday, June 17, 2011 3:12 AM
    Thursday, June 16, 2011 2:42 PM
  • First off that was the best and most exact explanation I needed so Thanks! 

     

    To add to the confusion I would like to test this with a VM first. I use VM player and it allows me to

    1. Bridges and option Replicate physical network.

    2. Host 

    3. NAT 

     

    If I have 3 VM's 1 being the server how should I configure the VM's? 

     

    Last question (hopefully) is I would like to do this remotely right now all the machines are receiving a IP from the Router (DHCP). Do you recommend being onsite if not then how should I proceed remotely?

     

    Thanks again 

    Thursday, June 16, 2011 3:01 PM
  • OK, for VM's it depends if your tests require integration with existing environment or it has to be run in "sand box" environment.

    In case that you want to run it in existing environment you need to configure each VM NICs as "bridged"

    In case that you want to use them in "sand box" configuration, you need to run NICs as "host"

    For remote reconfiguration, it's possible but you need to be careful :)

    First of all, when you plug in new DHCP server into your network, you have to enable one more option to prevent IP addresses conflict (becuase WIN DHCP doesn't know anything about current IP usgae within your network). For that, open DHCP management console and in server properties on "Advanced" tab configure "Conflict detection attempts" with value of 2. DHCP server will try to ping IP address twice before it will be issued to the client. If one of those pings would reply then it will not issue it. Next IP addess from the range will be taken and DHCP database will be updated.

    Then, next step is required. You should disable DHCP service on your router and reboot at least one DHCP client machine to get current lease from new DHCP server. Then try to access this machine to check if all issued settings are appropriate, Then reboot all machines to connect to new DHCP server or ask "someone" with administrative privileges in remote site to run on each DHCP client in command-line

    ipconfig /release

    ipconfig /renew

    Then DHCP lease will be issued without machine reboot.

    If you need more support do not hesitate to ask :)


    Regards, Krzysztof
    Friday, June 17, 2011 8:04 AM