General IAUG Discussion Forum

Expand all | Collapse all

Equinox Workplace

  • 1.  Equinox Workplace

    Posted 3 days ago
    Good morning,

    We recently implemented Avaya (Equinox) Workplace client and are having issues getting DNS entries with Verizon in the proper syntax so we can utilize auto-configuration.

    txt record and pointer records we submitted to Verizon are below




    Host name:


    Descriptive Name:

    Service: prod

    protocol: _avaya-ep-config

    Server Name:

    TTL: 300 sec

    Priority = 1

    Weight = 100

    Port = 443


    TXT record:

    Record Name: Prod





    Verizon replied with this below:

    A PTR record points an IP to a host name, not a host name to another host name.

     We also cannot add the last record, DNS does not deal with web protocols and URLs.

     Again, please confirm with your vendor who is asking for these records that the terminology is correct..."DNS SD entry" and "aads dns sd.txt" do not mean anything to us, unfortunately.

    Avaya has indicated the carrier may not be RFC 6763 compliant. We continue to work on this, but reaching out to see if anyone has implemented the auto configuration for equinox/workplace for clients and if you can share any input relating to DNS entry.

    Thank you for any input. Kathleen DeSantis 718-283-7899 Maimonides Medical Center

    Kathleen DeSantis
    Telecommunications Manager
    Maimonides Medical Center
    Brooklyn NY

  • 2.  RE: Equinox Workplace

    Posted 3 days ago
    We actually got away from the PTR as we have a lot of domains.  I  set up  an account on avaya cloud that redirects the workplace to  the AADS.   A lot easier than managing DNS records.


    Michael Goodwin
    Sr Comm Engineer
    Toll Brothers, Inc.

  • 3.  RE: Equinox Workplace

    Posted 3 days ago
    Hi Kathleen,

    We are using the Auto config feature of AADS for Workplace clients and the DNS records mentioned by you are correct and configured in a similar way on our external DNS servers.
    It seems Verizon is not RFC 6763 compliant, which is a mandatory prerequisite for auto config to work.

    Warm Regards,
    Arslan Ali Zaidi | |