[Top] [All Lists]

Re: new DNS classes

2017-07-09 11:44:25
On 8 Jul 2017, at 20:58, Mark Andrews wrote:

In message <EDFEF9A1-99CF-4F25-9C1C-051E78949967(_at_)qti(_dot_)qualcomm(_dot_)com>, Pete Resnic
k writes:
On 7 Jul 2017, at 19:18, Mark Andrews wrote:

Well use nsupdate.  That also ships with the Mac.

Of course doing that likely means I'll have records that don't show up in the server UI. Not entirely thrilling. And I could accomplish exactly
the same thing by directly editing the BIND config files, so I'm not
sure what that gains me in terms of "not hard to deploy".

Given Macs can register their own addresses in the DNS using UPDATE...

You mean an A or AAAA record, which the UI does support?

...Log a bug with Apple that the
tool doesn't support all known types and that it doesn't support
unknown types.

And in the meanwhile, you still say, "new RR types are not hard to deploy"?

We supply user applications to manipulate the DNS.  Those tools are
capable of updating yet to be defined types.  Putting a front end
on those tools that takes the new type someone dreams up is easy.

To quote a favorite line of mine, I grant the point: If things were different, they wouldn't be the same.

Creating these front ends apparently has not happened, so how does this address the point that new RR types are hard to deploy?

We also supply C libraries that can do the same thing.  No one needs
to wait to use a new type.

I refer the honourable gentleman to the answer I gave some moments ago.

Sure, it would be easy to write code to make tools exist that would make it be easy to deploy. Those tools do not currently exist. It is therefore still hard to deploy.

There are python and perl tools available that can also send update

I refer the honourable gentleman to the answer I gave some moments ago.

If you just want the new records to be a blob of text a shell script
like this will convert the record to unknown format suitable to be
used by nsupdate.

% sh junk
hello world
\# 11 68656C6C6F20776F726C64
% cat junk
read record
hex=`printf "%s" "$record" | hexdump -ve '/1 "%02X"'`
length=`printf "%s" "$hex" | wc -c`
length=`expr $length / 2`
echo '\#' $length $hex

You can create all DNS records similarly.  Building them up
field by field.

One can do something similar in any scripting language.

I think you have proved my point exceedingly well there.

So no it isn't hard to use a new type.

Nobody said "use". The word was "deploy". Until a huge number of hosting providers and OS vendors and tool writers get their act together writ large (and that includes tool vendors who require recompiles and/or fun shell scripts in order to have a remotely sane UI experience), deployment of a new RR type is hard.

You just need to stop waiting
for the stupid DNS hoster to do it for you and organise to do it

That does not solve the deployment problem.

Pete Resnick <>
Qualcomm Technologies, Inc. - +1 (858)651-4478

<Prev in Thread] Current Thread [Next in Thread>