Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: How to configure isc-dhcpd-server to update reverse zone
      without   client pre configuration? (Vladimir Skubriev)
   2. Re: Unknown clients allowed, no response to discovers
      (Simon Hobson)


----------------------------------------------------------------------

Message: 1
Date: Fri, 20 May 2016 09:28:23 +0300
From: Vladimir Skubriev <skubr...@cvisionlab.com>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: How to configure isc-dhcpd-server to update reverse zone
        without client pre configuration?
Message-ID:
        <CAGgnAKrJKa8TgS=qs04jxzyciyphuf_vrbzkgkutxs+vs4g...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Thank you. I tried your solution.

It does not resolv an issue. Reverse zone update not occurs, until the
client is configured with fqdn.fqdn

2016-05-19 22:40 GMT+03:00 Bill Shirley <b...@henagar.polymerindustries.biz>
:

> Maybe:
> group {
>     use-host-decl-names on;
>     option fqdn.fqdn = concat(config-option server.ddns-hostname, ".",
> config-option server.ddns-domainname);
>
>     host client {
>         hardware ethernet: 08:00:27:d8:78:e5
>         fixed-address client.example.lab;
>     }
>     host server {
>         hardware ethernet: xx:xx:xx:xx:xx:xx
>         fixed-address server.example.lab;
>     }
> }
>
> Bill
>
>
> On 5/18/2016 9:27 AM, Vladimir Skubriev wrote:
>
> How to configure isc-dhcpd-server to update reverse zone without client
> pre configuration?
>
> I'm trying to set up isc-dhcpd-server from ubuntu 16.04 (4.3.3-5ubuntu12)
> to configuring heterogeneous network with ubuntu, windows, macos, other ip
> devices.
>
> I'm already setuped bind to store ip address configuration of statically
> configured hosts in dns. My internal zone already has an A records like:
>
> client.example.lab a 900 192.168.1.10
> server.example.lab a 900 192.168.1.11
>
> Also I have statically defined hosts on dhcpd.conf like:
>
> host client {
> hardware ethernet: 08:00:27:d8:78:e5
> fixed-address client;
> }
>
> I don't want to update A records in my internal zone example.lab
> dynamically. Because this setup requires sustained attention to clean up
> zones because of update errors like 'YXDOMAIN, NXRRSET etc'
>
> I want to update dynamically only reverse zone of my internal subnet
> 192.168.1.0/24
>
> So I configured the dhcpd server as follows:
>
> ddns-updates on;
> do-forward-updates off;
>
> The documentation states that:
>
> do-forward-updates flag;
>
> ...
>
> If this statement is used to disable forward updates, the DHCP server will
> never attempt to update the client's A record, and will only ever attempt
> to update the client's PTR record if the client supplies an FQDN that
> should be placed in the PTR record using the fqdn option.
>
> I tried to setup this option manually on ubuntu in /etc/dhcp/dhclient.conf
> as follows:
>
> send fqdn.fqdn = "client.example.lab"
>
> In this case dhcpd server succesfully updates reverse PTR zone with this
> fqdn name. Also it is point the obtained ip to this fqdn name.
>
> But this workflow assumes that I need to configure each client in the net.
>
> Is there another way to configure isc-dhcp-server for retrive fqdn.fqdn
> from the server itself, without client pre-configuration?
>
> Is it is impossible now with isc-dhcp-server ?
>
>
>
> --
> Faithfully yours,
>
> CVision Lab System Administrator
> Vladimir Skubriev
>
>
> _______________________________________________
> dhcp-users mailing 
> listdhcp-us...@lists.isc.orghttps://lists.isc.org/mailman/listinfo/dhcp-users
>
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>



-- 
Faithfully yours,

CVision Lab System Administrator
Vladimir Skubriev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20160520/aa5b5e04/attachment-0001.html>

------------------------------

Message: 2
Date: Fri, 20 May 2016 11:01:14 +0100
From: Simon Hobson <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Unknown clients allowed, no response to discovers
Message-ID: <56c0cf75-af00-44b7-97c2-13407a5b1...@thehobsons.co.uk>
Content-Type: text/plain; charset=us-ascii

Ryan Goddard <rhinobe...@gmail.com> wrote:

> DHCP server V3.0.1rc12

You do realise just how ancient that version is don't you ? It's been 
deprecated for over 7 years, can't find out when it was actually superceded. 
The last extended support version of the 3.x branch has been deprecated for 
over 4 years.

> Requests from some CPEs (soho routers) attached to cable modems are showing 
> in the log as "unknown clients" - while in the dhcpd.conf unknown clients are 
> allowed for these subnets.
> What could be causing the server to respond to these discovers like this?
> 
> ex:
> May 19 15:19:16 server02 dhcpd: [ID 702911 local5.info] DHCPDISCOVER from 
> f8:32:e4:ae:33:10 via 66.207.2.1: unknown client
> 
> }
> subnet 66.207.2.0 netmask 255.255.255.0 {
> option broadcast-address 66.207.2.255;
> option routers 66.207.2.1;
> range 66.207.2.2 66.207.2.253;
> }

The extra { ... } hint that this is part of a bigger scope, might be a good 
idea to post more of the config.

But I think the only advice you are likely to get is update to something that's 
current.



------------------------------

_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users

End of dhcp-users Digest, Vol 91, Issue 23
******************************************

Reply via email to