From: Alexander Marx <alexander.marx@oab.de>
To: development@lists.ipfire.org
Subject: BUG 10262
Date: Wed, 05 Dec 2012 07:42:31 +0100 [thread overview]
Message-ID: <50BEECD7.2090104@oab.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
Dear List.
I confirmed Bug #10262.
The webinterface is programmed inconsistently. Under the OPENVPN
advanced options, the field "domain" is checked via
&General::validfqdnname which checks, if the domainname has two parts,
seperated by a dot.
under the DHCP options, the "domain" field is written into the CONF File
without any checks.
Which of the developers is responsible for the DHCP code?
AND: What is the GENERAL policy for a domain name?
Should there be just a name (which also needs to be checked) or do we
need to have a dot-sperarated domain name?
I don't know what is the RFC for this, but i think it should be in DNS
compatible form "domain.toplevel".
Any thoughts?
Alex
reply other threads:[~2012-12-05 6:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50BEECD7.2090104@oab.de \
--to=alexander.marx@oab.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox