On 23/04/2020 20:49, Simon Kelley wrote:
>
> According to RFC 4291 Para 2.2, a mixed representation is possible, for
> instance ipv6-mapped IPv4 addresses can be written as
>
> ::.1.2.3.4
>
> So you could use something like 2a01:ac00::$something:98.98.98.98
>
> and not have problems if
On 21/04/2020 14:58, William Edwards wrote:
> Hello,
>
> I am working on replacing static IP addresses in our network by static
> DHCP leases (which is in turn preparation for PXE). For IPv4, this is
> easily doable, but for IPv6 this is a bit of a challenge because of the
> following:
>
> In
On 4/22/2020 9:08 AM, William Edwards wrote:
>
>> Op 22 apr. 2020 om 08:41 heeft Olaf Hering het volgende
>> geschreven:
>>
>> Am Tue, 21 Apr 2020 15:58:25 +0200
>> schrieb "William Edwards" :
>>
>>> Ideas are welcome.
>>
>> You did not say how hosts are identified, nor did you say why exactly
>
> Op 22 apr. 2020 om 08:41 heeft Olaf Hering het volgende
> geschreven:
>
> Am Tue, 21 Apr 2020 15:58:25 +0200
> schrieb "William Edwards" :
>
>> Ideas are welcome.
>
> You did not say how hosts are identified, nor did you say why exactly
> addresses matter in your setup.
> If it is done bas
Am Tue, 21 Apr 2020 15:58:25 +0200
schrieb "William Edwards" :
> Ideas are welcome.
You did not say how hosts are identified, nor did you say why exactly addresses
matter in your setup.
If it is done based on their MAC addresses, just give each host a name.
host-record=hostname,hostname.${dns_d
Hello,
I am working on replacing static IP addresses in our network by static DHCP
leases (which is in turn preparation for PXE). For IPv4, this is easily doable,
but for IPv6 this is a bit of a challenge because of the following:
In our case, all services directly attached to the internet are