Skip to main content
A
Anonymous_User
Contributor III
June 8, 2007
Question

DHCP not passing dns to client

  • June 8, 2007
  • 2 replies
  • 1943 views
FG-60 as dhcp server. Wan1 gets static IP from ISP via DHCP. System ->Network ->Wan1 shows " Acquired DNS: 154.11.129.59 154.11.129.187 " Yet when I release and renew on my client pc, it is still retaining old values from previous experimentation (Level3' s) I have confirmed I do not have these Level3 values anywhere else on the FG, nor statically coded to the client. Have rebooted the FG and the clients, released/renewed same thing.

    2 replies

    rwpatterson
    rwpatterson
    New Member
    June 8, 2007
    Fortigates aren' t DNS servers, but can be used to proxy DNS requests (I believe). The PC has to be set to use the FGT as it' s DNS source. It won' t be picked up by the PC automatically. Personally, I use Linux DNS services and leave the FGT to route, and scan. That' s what it' s built for. Make sure you add DNS entries into the DHCP configuration in the FGT. Also run an ' IPCONFIG /FLUSHDNS' from the command prompt to clear out any artifacts that may be left over from the old DHCP configuration. ' IPCONFIG /RENEW' may take care of this as well.
    abelio
    SuperUser
    abelio
    SuperUser
    June 8, 2007
    If you use DHCP server for any interface, configure DNS settings (and WINS, etc) in DHCP server configuration for that iface (your own servers or isp dns servers) ISP' s acquired DNS servers are not automagically translated to internal dhcp leases.
    Terms & ConditionsAccessibility statement
    Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
    Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.