Is there a way to declare static hosts more smartest?

[Vladimir Skubriev]

Thank you.

I don't want to use DDNS. I just got rid of it )

I want to bind host ip with ip resolved by dhcpd server from DNS.

I want to keep data about relation of host and ip address in static DNS
zone. So to manually correct it, when neccessary.

To be honest my current ddns setup (you described it as second option) is
not stable within a few years of operation. Errors occur frequently
(YXDOMAIN, NXRRSET and so on). I have to constantly keep track of errors in
syslog and manually edit zone to remove a,txt records if something is
changed in the network (i.e client changed ip, not released ip an so on).

I can't find info what information is stored in txt records. It would be
cool if someone suggested ))

So I was disappointed in ddns ((.

Excusme for bad english. )



2016-05-24 16:18 GMT+03:00 dave c <dhcp at gvtc.drakkar.org>:

> You could drop down to something like this:
>
> host callisto {hardware ethernet 00:25:33:44:80:55; }
> {repeating for all hosts}
>
>
> And in your DHCP pools you can use the directive:
>
>     allow known hosts;
>
> Then only those hosts whose MAC addresses are predefined via host
> statements will get an address from DHCP (or from a specific pool in your
> subnet declarations). You could then use a dynamic dns update from the
> hosts back to your DNS server (or from DHCP to your DNS server) to make the
> host register itself into DNS.
>
> Second option I can think of, you could instead of using the system's
> hostname for the fixed-address, you could instead use the dotted 4 IP
> address and again turn on DNS update. Then you would only have to edit the
> DHCP hosts file instead of having to update DNS to predefine the hostnames
> -> dotted 4 IP connection and then use that hostname in the DHCP config.
>
> Other than that, we're not sure what it is you are trying to save.
>
> Dave
>
>
>
> On 5/24/16 05:39, Vladimir Skubriev wrote:
>
>> [something] same for all hosts.
>>
>> So not to duplicate host hostname in fixed-address.
>>
>> As you can see host declaration composed of identical blocks.
>>
>>
>>
>>
>> 2016-05-24 13:31 GMT+03:00 Simon Hobson <dhcp1 at thehobsons.co.uk <mailto:
>> dhcp1 at thehobsons.co.uk>>:
>>
>>     Vladimir Skubriev <skubriev at cvisionlab.com <mailto:
>> skubriev at cvisionlab.com>> wrote:
>>
>>     > Now I used following config strings:
>>     >
>>     > ...
>>     >   host callisto {
>>     >     hardware ethernet 00:25:33:44:80:55;
>>     >     fixed-address callisto;
>>     >   }
>>     > ...
>>     >
>>     > Is there a way not to be repeated in fixed-address and declaring
>> only host-decl-names in host [hostname] directive?
>>
>>     Sorry, I don't understand the question.
>>
>>     > Something like this:
>>     >
>>     > ...
>>     >   host callisto {
>>     >     hardware ethernet 00:25:33:44:80:55;
>>     >     fixed-address [something];
>>     >   }
>>     >
>>     >   host earth {
>>     >     hardware ethernet 14:99:88:71:77;
>>     >     fixed-address [something];
>>     >   }
>>     > ...
>>
>>     That will work, assuming that [something] represents either an IP
>> address, or something that
>>     resolves (via DNS lookup) to an IP address.
>>     _______________________________________________
>>     dhcp-users mailing list
>>     dhcp-users at lists.isc.org <mailto:dhcp-users at lists.isc.org>
>>     https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>>
>>
>>
>> --
>> Faithfully yours,
>>
>> CVision Lab System Administrator
>> Vladimir Skubriev
>>
>>
>>
>> _______________________________________________
>> dhcp-users mailing list
>> dhcp-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/dhcp-users
>>
>>
> --
> Dave Calafrancesco
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at 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/20160524/93a10b58/attachment.html>