Results 1 to 4 of 4

Thread: reverved TLD in examples cases problems.

  1. #1
    Senior Member
    Join Date
    Jan 2008
    Posts
    400

    reverved TLD in examples cases problems.

    Hai,

    Now i was reading :



    and all things refer to : ADSDOMAIN.LOCAL

    but a .local is a reserved TLD for apples mDNS ( zero conf )
    see :

    so please remove these bad examples for the docs.
    when you read :

    you can choose from :
    To safely satisfy these needs, four domain names are reserved as
    listed and described below.

    .test
    .example
    .invalid
    .localhost

    my advice, use the .example

    This saves a lots of problems in the future.

  2. #2
    Zarafa

    Join Date
    Jan 2009
    Location
    Hanover, Germany
    Posts
    1,891
    What kind of problems does this cause and do you want to prevent for the future?
    Regards Felix

    How to get Kopano

    Zarafa ALPHA/BETA/RC feedback in BETA forum please.
    Zarafa IRC chat: irc.freenode.com > #zarafa
    Zarafa documentation: http://documentation.zarafa.com/

    No support via PM! Please contact our sales team for an offer if you want my full attention.

  3. #3
    Senior Member
    Join Date
    Jan 2008
    Posts
    400
    Ok Felix,

    For example, ubuntu ( and lots of others, debian RH, Suse etc. )
    use mDNS, you setup a samba 4 domain ( with AD ) with zarafa in AD.
    your resolving can go wrong now.

    mDNS uses .local
    your AD domain uses .local
    Avahi daemon did prevent resolution of FQDNs ( this was a bug in avahi, but a hell to debug )

    nsswitch.conf used :
    hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
    again chance for problems..

    Kerberos now "sometimes" fails, i hell to look for and yes changing resolving orders helps in this case,
    im very active also on the samba mailing list and this was a big problem in the beginning with samba4 setups,
    so we re-ecudate everybody with the reserved TLDs.

    We had lots of problems with resolving due to .lan and .local

    and also, why do you see so much ".local" exchange domains which EHLO hostname.local ( WHICH IS VERY WRONG!! PEOPLE )
    due to fact its incorrectly use in the documentation, even microsoft corrected this ( after the mDNS registration of Apple). ( see also the RFC's for that )
    a EHLO hostname MUST be a resolvale hostname, with at least a A dns record. << resolvable hostname.
    is .local resolvable. NO, so preventing this is only good.

    So keeping documentations and settings as RFC specifies, helps a lot.

    and i.m.o. using .example lets people thing about there domainname. because nobody wants .example unless its an example. :-)

    A mail server setup isnt just a simpel setup, you need to know your DNS things, what A MX PTR RR records are, when to use them, where to use them.
    and it all starts with RTFM... ;-)
    so correct the documentation would be a good thing, and adding a refferral what is reserved in the Zarafa documentation would only improve Zarafa.

    ( ps. sorry for the typos im a dislextic. )
    Last edited by thctlo; 16-03-2016 at 04:51 PM.

  4. #4
    Zarafa

    Join Date
    Jan 2009
    Location
    Hanover, Germany
    Posts
    1,891
    You may be true with your points, but since we only explain the client side and never tell anyone to setup a domain ending in .local I still don't see the real problem. Nevertheless since the change is trivial I just renamed all the .local domains to .example.
    Regards Felix

    How to get Kopano

    Zarafa ALPHA/BETA/RC feedback in BETA forum please.
    Zarafa IRC chat: irc.freenode.com > #zarafa
    Zarafa documentation: http://documentation.zarafa.com/

    No support via PM! Please contact our sales team for an offer if you want my full attention.

Similar Threads

  1. Replies: 1
    Last Post: 25-07-2011, 08:31 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •