In article mailman.1898.1388124461.20661.bind-us...@lists.isc.org,
David C. Rankin drankina...@suddenlinkmail.com wrote:
It seems insane that any modern device would think spaces are a good idea
in
a hostname, but Nintendo obviously does. Is there any way to accommodate
this,
or
In article mailman.1898.1388124461.20661.bind-us...@lists.isc.org,
David C. Rankin drankina...@suddenlinkmail.com wrote:
It seems insane that any modern device would think spaces are a good idea
in
a hostname, but Nintendo obviously does. Is there any way to accommodate
this,
or should I
On 27 Dec 2013, at 06:07, David C. Rankin drankina...@suddenlinkmail.com
wrote:
Dec 26 20:55:43 nirvana dhcpd: Unable to add forward map from Nintendo Wii
U.3111skyline.com to 192.168.6.148: REFUSED
IIUC, your DHCP server seems to be handling the DDNS transaction.
If you can set the
On 27/12/13 11:16, Matus UHLAR - fantomas wrote:
I would ask nintendo to produce a release...
Ha ha ;o)
No, the only realistic option here is to override the client DDNS
hostname option with something sanitised. Since the client-supplied
hostname isn't even unique, let alone sane, I would
On 27/12/13 11:16, Matus UHLAR - fantomas wrote:
I would ask nintendo to produce a release...
On 27.12.13 14:56, Phil Mayers wrote:
Ha ha ;o)
No, the only realistic option here is to override the client DDNS
hostname option with something sanitised. Since the client-supplied
hostname isn't
From: David C. Rankin drankina...@suddenlinkmail.com
I have bind 9.9.1.P1-2 with dynamic updates from dhcp 4.2.3.2-2.
It has worked
great, but I've run into a problem with a dreaded kids-present that
I suspect is
due to the game console attempting to provide a hostname containing
I've been using bind 9.9 to do inline signing for a while
experimentally. The keys were initialized with a basic dnssec-keygen
$zone_name. I decided to upgrade the keys from sha1 to sha256 and from
nsec to nsec3; using the instructions at
https://kb.isc.org/article/AA-00711 I moved all the old
In message 52bdee40.2070...@peak.org, Alan Batie writes:
I've been using bind 9.9 to do inline signing for a while
experimentally. The keys were initialized with a basic dnssec-keygen
$zone_name. I decided to upgrade the keys from sha1 to sha256 and from
nsec to nsec3; using the
8 matches
Mail list logo