• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

DHCP issues

Scheduled Pinned Locked Moved DHCP and DNS
4 Posts 3 Posters 2.7k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L
    Leoandru
    last edited by Feb 12, 2006, 4:26 PM Feb 12, 2006, 4:12 PM

    I'm using static dhcp leases on my lan network to issue static ip to 2 machines. however when I turn on the dns fowarder option to register the DHCP leases (so that their hostnames can be resolved by the dns fowarder) the hostnames of these machines cannot be resolved.
    When I use static arp but allow an ip address to be allocated from the pool it works fine! the hostnames get registered and can be resolved.
    All other machines gets their hostnames registered except for those two that I assigned a static lease.
    Is this how it suppose to work? and if so is there a workaround?

    even though the ip address of some machines are statically leased I don't think everyone on the lan will remember the ip address so suggesting that won't solve my problem.

    I'm using:

    1.0-BETA1-TESTING-SNAPSHOT-2-8-06
    built on Wed Feb 8 23:02:48 UTC 2006

    1 Reply Last reply Reply Quote 0
    • H
      hoba
      last edited by Feb 12, 2006, 4:19 PM

      A workaround is to add the IPs and the hostnames to the DNS forwarder as the IPs are static this way.

      1 Reply Last reply Reply Quote 0
      • L
        Leoandru
        last edited by Feb 12, 2006, 4:29 PM

        ok thanks.. I tried editing the /etc/hosts file.. (even though a bad idea) I found that it was rewritten at reboot.

        1 Reply Last reply Reply Quote 0
        • T
          tristano
          last edited by Aug 3, 2006, 3:14 PM

          @hoba:

          A workaround is to add the IPs and the hostnames to the DNS forwarder as the IPs are static this way.

          I have to follow the same workaround on 1.0 RC2 to get this to work. Isn't this a problem? It seems to me that setting a static lease should make it easier for the router to find a particular client. Configuring a DNS override for each static DHCP lease is a bit of a hassle and will only lead to configuration errors as networks grow and change.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received