Just ran into this fun issue: after running "nsd-control addzone echo
example.tld patternname" (note the falsely inserted 'echo'), no
warning is raised, and the zonelist file contains:
# NSD zone list
# name pattern
add echo example.tld patternname
which again results in a lot of errors in the log file:
2013-01-31T16:23:35+01:00 julie nsd[25108]: xfrd: zone echo
example.tld received error code SERVER NOT AUTHORITATIVE FOR ZONE from
217.149.195.119
2013-01-31T16:23:35+01:00 julie nsd[25108]: xfrd: zone echo
example.tld bad transfer 0 from 217.149.195.119
I'm not sure whether spaces are allowed in idn zones or other vanity
RFCs, but I'd prefer to quote a domain name with spaces, when I really
intend to use it
Just ran into this fun issue: after running "nsd-control addzone
echo example.tld patternname" (note the falsely inserted 'echo'),
no warning is raised, and the zonelist file contains:
Yes it allows for whitespace in the zone name (but not the pattern name).
# NSD zone list # name pattern add echo example.tld patternname
which again results in a lot of errors in the log file:
2013-01-31T16:23:35+01:00 julie nsd[25108]: xfrd: zone echo
example.tld received error code SERVER NOT AUTHORITATIVE FOR ZONE
from 217.149.195.119 2013-01-31T16:23:35+01:00 julie nsd[25108]:
xfrd: zone echo example.tld bad transfer 0 from 217.149.195.119
I'm not sure whether spaces are allowed in idn zones or other
vanity RFCs, but I'd prefer to quote a domain name with spaces,
when I really intend to use it
No such RFCs. Can I label this a feature, or should NSD reject zone
names with spaces in them? quotes and stuff gets removed by the shell.
[ Quoting <wouter@nlnetlabs.nl> in "Re: [nsd-users] nsd4.0.0beta3: nsd-..." ]
> I'm not sure whether spaces are allowed in idn zones or other
> vanity RFCs, but I'd prefer to quote a domain name with spaces,
> when I really intend to use it
No such RFCs. Can I label this a feature, or should NSD reject zone
names with spaces in them? quotes and stuff gets removed by the shell.
nlnet\032labs.nl. is a completely valid zone name.
Without going quite that far I have to say that I do not think that the CLI interface to a nameserver implementation is the place to make restrictions to what is clearly allowed by the DNS protocol.
I.e. while I will most certainly not send my mother to the web shop URL above (for all sorts of reasons) I would like to be able to manage such a domain name via nsd-control.
Speaking of restrictions... I know a TLD that used to implement a strict limit (32 octets) to the length of domain names. The reason was primarily to make their implementation simpler and the justification was "no one used it" (at the time, which was long ago). And now we have IDN and in some parts of the namespace 32 characters is not all that uncommon.
Restrictions that are stricter than what the protocol allows may sometimes be necessary (it could be that something is really, really hard to implement otherwise). So be it. But restrictions based on "no one uses it" seems like the wrong thing to me. That's like hearing english-speaking people claim that ASCII is all you need because THEY don't use korean much
