One thing I have to comment to ".home.arpa", as I have changed any device used in my residental home network to use ".home.arpa" instead of ".local" or ".home", but I noticed one thing in connection with BIND
(I'm using just simple DNS with BIND)

I'm using DDNS and my router has there the dynamic master zones:
lets say "ddns.mynet.home.arpa" for forward DNS
and "1.168.192.in-addr.arpa" for reverse DNS;

on the second running DNS (also running BIND) which is just a VM
I could define there just a forward zone like this:

zone "1.168.192.in-addr.arpa" IN {
type forward;
forwarders { 192.168.0.1; };
forward only;
};

but with the forward zone "ddns.mynet.home.arpa" this doen't work, and I don't know if there are
any restrictions which shouldn't be in BIND ...

the reason for just defining a forward zone instead of slave zone on the second DNS is a timing thing:

at the moment a device gets registrated on the master DNS by DHCP, requests to the second DNS just get forwarded to the master and so get an reply, but with a slave zone requests to the second DNS
get resolved a longer time later ...

and this MUST work with ".home.arpa" the same way as with "168.192.in-addr.arpa" ...

these statements:

disable-empty-zone "HOME.ARPA";
disable-empty-zone "168.192.IN-ADDR.ARPA";

work both; or do I have to give this:

disable-empty-zone "MYNET.HOME.ARPA";

in order to work properly with forward zones?

Thanks,
Walter

On 04.07.2017 11:32, Ray Bellis wrote:
Given the relatively large number of changes in this document based on
Suzanne's review and my own, I'm starting a *one week* WGLC on this
document before it gets pushed back out to our AD again.

There was very little response to the last WGLC so there are concerns
over whether it has WG consensus.

*Please* read this version, and comment, even if it's to say "I have no
comments, please go ahead and publish".

NB: the particular string applied for (".home.arpa") is not up for
discussion again.  We've been there, done that.

thanks,

Ray

--8<--8<--

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Home Networking of the IETF.

         Title           : Special Use Domain '.home.arpa'
         Authors         : Pierre Pfister
                           Ted Lemon
        Filename        : draft-ietf-homenet-dot-09.txt
        Pages           : 9
        Date            : 2017-07-03

Abstract:
    This document specifies the behavior that is expected from the Domain
    Name System with regard to DNS queries for names ending with
    '.home.arpa.', and designates this domain as a special-use domain
    name. 'home.arpa' is designated for non-unique use in residential
    home networks.  Home Networking Control Protocol (HNCP) is updated to
    use the '.home.arpa' domain instead of '.home'.



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to