SRV Record for TC Software(SX20,C20)

Hi all,
We tested DNS SRV record for two VCS-Cs that are not clustered.
MCU works fine with those SRV records, but C20, SX20 do not work.
Can't TC endpoints receive SRV records?
VCS:X8.2.1
MCU5300:4.5(1.45)
C20,SX20:TC7.2.0
Best Regards,
Kotaro

Hi Patrick,
Sorry for the late reply.
I mentioned "MCU works fine with those SRV records, " but actually it didn't work.
The MCU just received two GKs IP addresses as Alternative Gatekeeper.
Now we use records below.
We configure "vcs1.test.local" as an SX20's Gatekeeper.
But when "vcs1.test.local" fails, the SX20 never register with "vcs2.test.local".
=====DNS Records=====
vcs1.test.local(A) and its Pointer record.
vcs2.test.local(A) and its Pointer record.
_h323cs._tcp.test.local
priority=1
weight=0
port=1720
svr hostname=vcs1.test.local
_h323cs._tcp.test.local
priority=10
weight=0
port=1720
svr hostname=vcs2.test.local
_h323ls._udp.test.local
priority=1
weight=0
port=1719
svr hostname=vcs1.test.local
_h323ls._udp.test.local
priority=10
weight=0
port=1719
svr hostname=vcs2.test.local
_h323rs._udp.test.local
priority=1
weight=0
port=1719
svr hostname=vcs1.test.local
_h323rs._udp.test.local
priority=10
weight=0
port=1719
svr hostname=vcs2.test.local
Best Regards,
Kotaro

Similar Messages

  • Need Clarification on how to provide SRV record for Director pool in Lync 2013 environment

    Hi ,
         I am Deploying an Lync Enterprise edition server with high redundancy, I have already deployed the below servers,
    fepool1.xxx.com, fepool2.xx.com, Exum.xx.com, RootAD.xx.com,
    CA.xx.com, Sql01.xxx.com, Sql02.xxx.com.
     I have already deployed frontend pool, Now I trying Depoly director pool with the set up., But My replication Status is Failed for director server.
    In DNS  , A records is created as below,
    dir01 Host A   10.221.10.107
    dir02 Host A 10.221.10.108
    dir Host A   10.221.10.107
    dir Host A 10.221.10.108
    Pls suggest me, What I need to add in SRV record.... for DNS load Balancing
    Thanks,
    Rajarajan

    Lync Client Trace,
    05/27/2014|06:13:01.341 A85C:1E7D4 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    05/27/2014|06:13:01.341 A85C:1E7D4 ERROR :: ResolveHostNameUsingGetAddrInfo - getaddrinfo(sipinternal.polyvineyard.com) failed hr=0x80072AF9
    05/27/2014|06:13:01.341 A85C:1E7D4 WARN  :: ResolveHostName - getaddrinfo failed for sipinternal.polyvineyard.com hr=0x80072AF9
    05/27/2014|06:13:01.341 A85C:1E7D4 ERROR :: ResolveHostNameUsingDnsQuery - DnsQuery(sipinternal.polyvineyard.com) failed error=9003
    05/27/2014|06:13:01.341 A85C:1E7D4 WARN  :: ResolveHostName - DNS lookup failed for sipinternal.polyvineyard.com hr=0x80004005
    05/27/2014|06:13:01.341 A85C:1E7D4 ERROR :: ResolveHostName - Name resolution for sipinternal.polyvineyard.com failed
    05/27/2014|06:13:01.341 A85C:1E7D4 ERROR :: ResolveHostSync ResolveHostName failed 8000ffff
    05/27/2014|06:13:01.341 A85C:1E7D4 ERROR :: DNS_RESOLUTION_WORKITEM::ProcessWorkItem ResolveHostName failed 8000ffff
    05/27/2014|06:13:01.342 A85C:847C TRACE :: HTTPPROXYCB:internetStatus 0x46
    05/27/2014|06:13:01.342 A85C:847C TRACE :: HTTPPROXYCB:internetStatus 0x46
    05/27/2014|06:13:01.343 A85C:1086C TRACE :: SIP_MSG_PROCESSOR::OnDnsResolutionComplete[000000F8B1D85350] Entered host sipinternal.polyvineyard.com
    05/27/2014|06:13:01.343 A85C:1086C ERROR :: SIP_MSG_PROCESSOR::OnDnsResolutionComplete - error : 80ee0066
    05/27/2014|06:13:01.343 A85C:1086C INFO  :: Use proxy server cache:1
    05/27/2014|06:13:01.343 A85C:1086C INFO  :: Unable to find routable Ipv4 address from proxy server list. Attempting to find one from proxy server cache list.
    05/27/2014|06:13:01.343 A85C:1086C WARN  :: Unable to find local routable Ipv4 address for SIP proxy server
    05/27/2014|06:13:01.343 A85C:1086C TRACE :: SIP_MSG_PROCESSOR::UseAutoHttpProxy try resolve HttpProxy
    05/27/2014|06:13:01.344 A85C:1086C TRACE :: HTTPPROXYCB:internetStatus 0x3c
    05/27/2014|06:13:01.344 A85C:1086C TRACE :: HTTPPROXYCB:internetStatus 0x3c
    05/27/2014|06:13:01.344 A85C:847C TRACE :: HTTPPROXYCB:internetStatus 0x50
    05/27/2014|06:13:01.344 A85C:847C TRACE :: HTTPPROXYCB:internetStatus 0xa
    05/27/2014|06:13:01.346 A85C:847C TRACE :: HTTPPROXYCB:request Complete result(0x0) error(0x2ee7)
    05/27/2014|06:13:01.346 A85C:1086C ERROR :: SIP_MSG_PROCESSOR::OnDnsResolutionComplete - setting m_RequestConnectionErrorCode to 0. Old value is 80ee0066
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: deleting Async workitem 000000F8C25E9368
    05/27/2014|06:13:01.347 A85C:1086C ERROR :: HTTP_PROXY_RESOLVE_CONTEXT::~HTTP_PROXY_RESOLVE_CONTEXT HPContext handle 1b deleted, this 000000F8BD164320
    05/27/2014|06:13:01.347 A85C:1086C TRACE :: HTTPPROXYCB:internetStatus 0x46
    05/27/2014|06:13:01.347 A85C:1086C TRACE :: HTTPPROXYCB:internetStatus 0x46
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: SIP_MSG_PROCESSOR::OnRequestConnectionConnectComplete - Enter this: 000000F8B1D85350, callid=(null), ErrorCode: 0x80ee001c
    05/27/2014|06:13:01.347 A85C:1086C ERROR :: Releasing connection and notifying transactions
    05/27/2014|06:13:01.347 A85C:1086C ERROR :: SIP_MSG_PROCESSOR::NotifyRequestConnectionConnectComplete - Error: 80ee001c
    05/27/2014|06:13:01.347 A85C:1086C ERROR :: OUTGOING_TRANSACTION::OnRequestConnectionConnectComplete - connection failed error 80ee001c
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: REGISTER_CONTEXT:State (4) => (5)
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: REGISTER_CONTEXT(b1d85350) SetAndNotify Recv(6) at State (5)
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: REGISTER_CONTEXT:State (5) => (6)
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: SIP_REGISTER:State (1) => (0)
    05/27/2014|06:13:01.347 A85C:1086C TRACE :: CUccServerEndpoint::UpdateEndpointState - Update state from 1 to 0. Status 80EE001C. Status text (null).
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: Function: CUccServiceOperationManager::DisableServManager
    05/27/2014|06:13:01.347 A85C:1086C TRACE :: Condition failed with 80ee0061: 'm_fServMgrEnabled'
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: Function: CUccServerEndpoint::UpdateEndpointState
    05/27/2014|06:13:01.347 A85C:1086C ERROR :: HRESULT API failed: 80ee0061 = hr. DisableServManager
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: CUccDnsResolverManager::Stop MR-INFO - [000000F8C29BC120] DNS resolver manager stopped
    05/27/2014|06:13:01.347 A85C:1086C INFO  :: ~Out trxn corr-id (000000F8C2428AA0)
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: UCCP:ClientAllowedAuthProts0x1000c
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: CUccServerSignalingSettings::put_AllowedHttpProxyAuthenticationModes set auth modes 0x1f
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: CUccDnsResolverManager::Start MR-INFO - [000000F8C29BC120] DNS resolver manager started
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: UCCP:NegotiatedAuthProt0x0
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: UCCP:ServerAuthProts0x0
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: CUccPrincipalServerEndpoint::GetSipProviderProfile - Found no http proxy creds
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: SIP_ENDPOINT::SetSipAuthBroker (000000F8C2477760) _IUccSipAuthBroker(0x0000000000000000)
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: UCCP:ServerAuthProts0x0
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: SIP_AUTH(c2477e40) PrepareAuth at state: 0
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: SIP_REGISTER:State (0) => (1)
    05/27/2014|06:13:01.349 A85C:1086C INFO  :: Outgoing 000000F8B1D85350-<sip:[email protected]>, local=(null)
    05/27/2014|06:13:01.350 A85C:1086C INFO  :: Function: StringToSockAddress
    05/27/2014|06:13:01.350 A85C:1086C ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    05/27/2014|06:13:01.350 A85C:1086C INFO  :: Created Async workitem 000000F8C25E64E8, txn timeout 0, time sensitive 0, txn (0000000000000000)
    05/27/2014|06:13:01.350 A85C:1E7D4 INFO  :: Function: StringToSockAddress
    05/27/2014|06:13:01.350 A85C:1E7D4 ERROR :: HRESULT failed: 80072726 = HRESULT_FROM_WIN32(::ShimWSAGetLastError()) . Failed to convert string IP to SOCKADDR
    05/27/2014|06:13:01.352 A85C:1E7D4 ERROR :: ResolveHostNameUsingGetAddrInfo - getaddrinfo(sip.polyvineyard.com) failed hr=0x80072AF9
    05/27/2014|06:13:01.352 A85C:1E7D4 WARN  :: ResolveHostName - getaddrinfo failed for sip.polyvineyard.com hr=0x80072AF9
    05/27/2014|06:13:01.352 A85C:1E7D4 ERROR :: ResolveHostNameUsingDnsQuery - DnsQuery(sip.polyvineyard.com) failed error=9003
    05/27/2014|06:13:01.352 A85C:1E7D4 WARN  :: ResolveHostName - DNS lookup failed for sip.polyvineyard.com hr=0x80004005
    05/27/2014|06:13:01.352 A85C:1E7D4 ERROR :: ResolveHostName - Name resolution for sip.polyvineyard.com failed
    Please help me add correct entries into DNS. 
    /Rajan

  • Does iOS support SRV records for Active Sync autodiscovery?

    See http://support.microsoft.com/kb/940881#
    From my testing, the answer is "no".  I'm sure my SRV records are correct, but when adding an account in iOS the user is still prompted for a server address.  Has anyone made this work?

    Hello!
    The GSS itself only supports A records, meaning it only responds to that type of query from a client.  You can configure an NS forwarder to push non-A records to another server that can handle it.  As well, you can run CNR in conjunction with the GSS which will respond to MX, SRV, and NS records. Some versions of GSS code allowed you to run CNR on the GSS itself. (CNR = Cisco Network Registrar).
    More specifically to your question - CNR supports RFC 2052 (SRV records) and is fully interoperable with Dynamic DNS SRV records (RFC 2782).
    Regards,
    Chris Higgins

  • How do I add SRV record to my DNS for Office 365?

    How do I add the following record?
    Add the SIP SRV record for Lync web conferencing.
    Create a new SRV record.
    In the new record, make sure that the fields are set to precisely the following values:
    Record Type: SRV
    Service: _sip
    Protocol: _tls
    Port: 443
    Weight: 1
    Priority: 100
    TTL: Set this value to 1 hour or to the equivalent in minutes (60), seconds (3600), etc.
    Name: @
    Target: sipdir.online.lync.com
    Save the record.
    Need help ASAP because my clients Email is down when I changed Domain Name Servers to Business Catalyst.
    All Office 365 functions were lost.
    Thank you for some assistance - URGENT,
    Jim Vernon
    Hopegate Software

    Here is an image of the settings that Office 365 says i need to correct in my DNS settings on Business Catalyst:

  • SRV record required for sip communication?

    I'm in the process of starting up a lync 2013 deployment while we have an existing OCS 2007 R1 environment running. I'm getting numerous errors and the Front end service won't start.  Some errors report:
    Cause: The Mediation Server service cannot communicate with the Front End Service over SIP due to network connectivity issues.
    Currently in Lync 2013 I have A records and an alias as following pointing to a HLB VIP.  All the following records are pointing to the same IP which is has all ports open.
    Host
    lyncpool01.domain.com
    Alias (CNAME)
    LyncDiscoverInternal.domain.com
    A
    meet.domain.com
    A
    dialin.domain.com
    A
    LyncAdmin.domain.com
    Since I have an OCS 2007R1 environment running I can't use the same srv record for _sipinternalstls.

    ready.
    I just got done running through the entire upgrade for everything including the BE DB.  Stopped all services, ran the gui upgrade, broke the mirrored database and did the upgrade, reenabled it, etc.
    So I verified my upgrade with my standard ed test environment and all version numbers look good now.
    Still can't start services.  RTCSRV failed to start within expected timeframe.
    also:
    Log Name:      Lync Server
    Source:        LS Mediation Server
    Date:          3/31/2014 3:27:31 PM
    Event ID:      25053
    Task Category: (1030)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      lvhlyncfe01.lvh.com
    Description:
    The description for Event ID 25053 from source LS Mediation Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    lyncpool01.lvh.com
    False
    Microsoft.Rtc.Signaling.ConnectionFailureException:Unable to establish a connection. ---> System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.17.171.125:5061
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at Microsoft.Rtc.Internal.Sip.TcpTransport.OnConnected(Object arg)
    --- End of inner exception stack trace ---
       at Microsoft.Rtc.Signaling.SipAsyncResult2`1.ThrowIfFailed()
       at Microsoft.Rtc.Signaling.SipAsyncResultBase2.EndAsyncOperation[TResult](Object owner, IAsyncResult result)
       at Microsoft.RTC.MediationServerCore.PeriodicOptionsSender.FinishSendOptionMessage(IAsyncResult ar)
    Detected at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
       at System.Environment.get_StackTrace()
       at Microsoft.Rtc.Signaling.RealTimeException..ctor(String message, Exception innerException)
       at Microsoft.Rtc.Signaling.ExceptionUtilities.TryMapS4Exception(Exception s4Exception, SecurityAssociationContext securityContext, Boolean isSipEndpoint, String traceId, Object parentObject, Object childObject, RealTimeException& ex)
       at Microsoft.Rtc.Signaling.SipTransactionAsyncResult`1.ConnectionConnectCompleted(IAsyncResult result)
       at Microsoft.Rtc.Signaling.SipAsyncResult2`1.MakeCallback()
       at Microsoft.Rtc.Signaling.SipAsyncResult2`1.Complete(TEx ex, Boolean synchronousCompletion)
       at Microsoft.Rtc.Signaling.RealTimeConnection.CompletePendingConnects(IEnumerable`1 results, RealTimeException exception)
       at Microsoft.Rtc.Signaling.RealTimeConnection.<.ctor>b__1(SipConnection sender, Object reason)
       at Microsoft.Rtc.Internal.Sip.SipConnection.FireDisconnectedEvent(Object reason)
       at Microsoft.Rtc.Internal.Sip.SingleThreadedDispatcherQueue.DispatcherCallback(Object queue)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
    The handle is invalid
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="LS Mediation Server" />
        <EventID Qualifiers="50182">25053</EventID>
        <Level>2</Level>
        <Task>1030</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-03-31T19:27:31.000000000Z" />
        <EventRecordID>1466</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>lvhlyncfe01.lvh.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>lyncpool01.lvh.com</Data>
        <Data>False</Data>
        <Data>Microsoft.Rtc.Signaling.ConnectionFailureException:Unable to establish a connection. ---&gt; System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.17.171.125:5061
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at Microsoft.Rtc.Internal.Sip.TcpTransport.OnConnected(Object arg)
    --- End of inner exception stack trace ---
       at Microsoft.Rtc.Signaling.SipAsyncResult2`1.ThrowIfFailed()
       at Microsoft.Rtc.Signaling.SipAsyncResultBase2.EndAsyncOperation[TResult](Object owner, IAsyncResult result)
       at Microsoft.RTC.MediationServerCore.PeriodicOptionsSender.FinishSendOptionMessage(IAsyncResult ar)
    Detected at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
       at System.Environment.get_StackTrace()
       at Microsoft.Rtc.Signaling.RealTimeException..ctor(String message, Exception innerException)
       at Microsoft.Rtc.Signaling.ExceptionUtilities.TryMapS4Exception(Exception s4Exception, SecurityAssociationContext securityContext, Boolean isSipEndpoint, String traceId, Object parentObject, Object childObject, RealTimeException&amp; ex)
       at Microsoft.Rtc.Signaling.SipTransactionAsyncResult`1.ConnectionConnectCompleted(IAsyncResult result)
       at Microsoft.Rtc.Signaling.SipAsyncResult2`1.MakeCallback()
       at Microsoft.Rtc.Signaling.SipAsyncResult2`1.Complete(TEx ex, Boolean synchronousCompletion)
       at Microsoft.Rtc.Signaling.RealTimeConnection.CompletePendingConnects(IEnumerable`1 results, RealTimeException exception)
       at Microsoft.Rtc.Signaling.RealTimeConnection.&lt;.ctor&gt;b__1(SipConnection sender, Object reason)
       at Microsoft.Rtc.Internal.Sip.SipConnection.FireDisconnectedEvent(Object reason)
       at Microsoft.Rtc.Internal.Sip.SingleThreadedDispatcherQueue.DispatcherCallback(Object queue)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()</Data>
      </EventData>
    </Event>

  • Lync on premises with Exchange online UM SRV record

    Hi,
    We have Lync 2013 on premises and we have Hybrid exchange deployment, recently we have integrated Lync on premises with Exchange online UM, we have configured subscriber access and I have done all configuration, created hosted voice mail policy, created
    Subscriber access UM contact.
    Problem is that if a user dials from Lync client to voice mail (Exchange online UM Subscriber Access number) the call successfully establish, if the same user is outside the organization and wants to call the Exchange online UM Subscriber
    Access number from his mobile or from his home phone number the call doesn't connect, this problem is not from the same user any one from outside the organization can not call to subscriber access number from his mobile or from his landline (outside the organization
    numbers)
    I have done some logging on Lync Edge server and found two things:
    When a user calls from Lync client to O365 UM Subscriber access the call establish successfully and when I see the call logs I am seeing the
    [email protected] and SRV record for the domain.com is verified
    When a user calls from outside the organization (Landline or mobile) to O365 UM subscriber access the call doesn't establish and when I see the call logs I am seeing
    [email protected] and subscriber access number as
    [email protected] and the error says Unable to resolve DNS SRV record for domain it.domain.com.
    Please note our internal domain is it.domain.com and our external or smtp domain is domain.com
    In Lync 2013 the default sip domain is also it.domain.com and additional sip domain is domain.com
    Pleasae help me to resolve the issue.
    If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

    The issue is that your default domain is it.domain.com. I suspect that even if your Edge server is able to route this call back to Exchange online, that tenant will reject this call as it will not be able to find it.domain.com or federation SRV record associated
    with it.
    You will need to change your default SIP domain to your public SIP domain. If you decide to do this, please note that you will also need to review any impact on the simple URLs (and certificates if applicable).
    It is also recommended to perform an export-csconfiguration command to backup the topology before making these changes.
    Hope this helps.
    SinghP80

  • Error: Missing SRV record at DNS server - [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

    in an attempt to transfer FSMO roles to the 2012r2 DC the first thing I ran was dcdiag /e /c /v and after correcting some minor errors, I came upon this one in the DNS portion where a SRV record is missing and I have no idea how to fix/remove this. there's
    only two DCs, 200.5 and 200.6 where the former is a Hyper-V VM running 2012r2 and the latter is a physical 2003r2 machine. I was able to successfully raise the levels to 2003 and join the 2012r2 DC. this missing SRV record does not look fatal and only warrants
    a warning from dcdiag, however I would like to fix this so there's no trouble down the road. I've tried ipconfig /registerdns, but no dice. here is the message I'm concerned about:
                        Error:
                        Missing SRV record at DNS server 192.168.200.5:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
    the bottom portion of the DNS section that contains this message is in the RReg section and is as follows:
                  TEST: Dynamic update (Dyn)
                     Test record dcdiag-test-record added successfully in zone cmedia.local
                     Test record dcdiag-test-record deleted successfully in zone cmedia.local
                  TEST: Records registration (RReg)
                     Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
                        Matching CNAME record found at DNS server 192.168.200.5:
                        a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.5:
                        CM-DC1-HV-NYC01.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.cmedia.local
                        Error:
                        Missing SRV record at DNS server 192.168.200.5:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._udp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kpasswd._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.gc._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.5:
                        gc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                        Matching CNAME record found at DNS server 192.168.200.6:
                        a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.6:
                        CM-DC1-HV-NYC01.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.cmedia.local
                        Error:
                        Missing SRV record at DNS server 192.168.200.6:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._udp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kpasswd._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.gc._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.6:
                        gc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                  Warning: Record Registrations not found in some network adapters

    Hi Ace Fekay, thank you for your help. I hope you're still with me despite my lack of responding. I needed time to move the VPN server from the DC to a separate VM and then following your instructions to disable WINS Proxy and IP routing. Some of the delay
    was when I had to restart the 2003r2 server after disabling those two items since that cause DNS queries to the Internet to go unresolved with only the 2012r2 server. That's been corrected, but running dcdiag /c /e /v still gives some DNS problems. Here's
    the latest run of that...
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
                   Starting test: DNS
                      See DNS test in enterprise tests section for results
                      ......................... CM-DC-NY01 passed test DNS
             See DNS test in enterprise tests section for results
             ......................... CM-DC1-NY01 passed test DNS
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : cmedia
          Starting test: CheckSDRefDom
             ......................... cmedia passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... cmedia passed test CrossRefValidation
       Running enterprise tests on : cmedia.local
          Starting test: DNS
             Test results for domain controllers:
                DC: cm-dc-NY01.cmedia.local
                Domain: cmedia.local
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      The OS Microsoft(R) Windows(R) Server 2003, Standard Edition (Service Pack level: 2.0) is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
                         MAC address is 00:00:00:00:00:00
                         IP Address is static
                         IP address: 192.168.200.6
                         DNS servers:
                            192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
                            192.168.200.5 (CM-DC1-NY01) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
                         Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
                         Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                         Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
                         Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
                         Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
                         Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
                         Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
                   TEST: Delegations (Del)
                      Delegation information for the zone: cmedia.local.
                         Delegated domain name: _msdcs.cmedia.local.
                            DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
                   TEST: Dynamic update (Dyn)
                      Test record dcdiag-test-record added successfully in zone cmedia.local
                      Test record dcdiag-test-record deleted successfully in zone cmedia.local
                   TEST: Records registration (RReg)
                      Network Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
                         Matching CNAME record found at DNS server 192.168.200.6:
                         406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         cm-dc-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.6:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.pdc._msdcs.cmedia.local
                         Matching CNAME record found at DNS server 192.168.200.5:
                         406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         cm-dc-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.5:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.pdc._msdcs.cmedia.local
                   Warning: Record Registrations not found in some network adapters
                DC: CM-DC1-NY01.cmedia.local
                Domain: cmedia.local
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.0) is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000010] Microsoft Hyper-V Network Adapter:
                         MAC address is 00:00:00:00:00:00
                         IP Address is static
                         IP address: 192.168.200.5, 0000::0000:0000:0000:0000
                         DNS servers:
                            192.168.200.5 (CM-DC1-NY01) [Valid]
                            192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
                         Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 128.9.0.107 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
                         Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                         Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 128.8.10.90 [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
                         Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
                         Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
                         Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
                         Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
                         Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
                         Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
                         Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
                   TEST: Delegations (Del)
                      Delegation information for the zone: cmedia.local.
                         Delegated domain name: _msdcs.cmedia.local.
                            DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
                   TEST: Dynamic update (Dyn)
                      Test record dcdiag-test-record added successfully in zone cmedia.local
                      Test record dcdiag-test-record deleted successfully in zone cmedia.local
                   TEST: Records registration (RReg)
                      Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
                         Matching CNAME record found at DNS server 192.168.200.5:
                         a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         CM-DC1-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.5:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching CNAME record found at DNS server 192.168.200.6:
                         a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         CM-DC1-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.6:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                   Warning: Record Registrations not found in some network adapters
             Summary of test results for DNS servers used by the above domain controllers:
                DNS server: 198.32.64.12 (l.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12               [Err
    or details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:1::803f:235               [Error details: 1460 (Type: Win32 - Description: This operation ret
    urned because the timeout period expired.)]
                DNS server: 2001:500:2::c (c.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2::c               [Error details: 1460 (Type: Win32 - Description: This operation returned b
    ecause the timeout period expired.)]
                DNS server: 2001:500:2d::d (d.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2d::d               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:500:84::b (b.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:84::b               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:503:ba3e::2:30               [Error details: 1460 (Type: Win32 - Description: This operation retu
    rned because the timeout period expired.)]
                DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:503:c27::2:30               [Error details: 1460 (Type: Win32 - Description: This operation retur
    ned because the timeout period expired.)]
                DNS server: 2001:7fd::1 (k.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:7fd::1               [Error details: 1460 (Type: Win32 - Description: This operation returned bec
    ause the timeout period expired.)]
                DNS server: 128.8.10.90 (d.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90               [Erro
    r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 128.9.0.107 (b.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.9.0.107               [Erro
    r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:2f::f (f.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2f::f               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:500:3::42 (l.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:3::42               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:7fe::53 (i.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:7fe::53               [Error details: 1460 (Type: Win32 - Description: This operation returned be
    cause the timeout period expired.)]
                DNS server: 2001:dc3::35 (m.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:dc3::35               [Error details: 1460 (Type: Win32 - Description: This operation returned be
    cause the timeout period expired.)]
                DNS server: 128.63.2.53 (h.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.112.36.4 (g.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.168.200.5 (CM-DC1-NY01)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
                DNS server: 192.168.200.6 (cm-dc-NY01.cmedia.local.)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
                   DNS delegation for the domain  _msdcs.cmedia.local. is operational on IP 192.168.200.6
                DNS server: 192.203.230.10 (e.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.228.79.201 (b.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.33.4.12 (c.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.36.148.17 (i.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.5.5.241 (f.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.58.128.30 (j.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 193.0.14.129 (k.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 198.41.0.4 (a.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 199.7.83.42 (l.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 199.7.91.13 (d.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 202.12.27.33 (m.root-servers.net.)
                   All tests passed on this DNS server
             Summary of DNS test results:
                                                Auth Basc Forw Del  Dyn  RReg Ext
                Domain: cmedia.local
                   cm-dc-NY01                  PASS PASS PASS PASS PASS WARN n/a
                   CM-DC1-NY01                 PASS PASS PASS PASS PASS WARN n/a
             ......................... cmedia.local passed test DNS
          Starting test: LocatorCheck
             GC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             PDC Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             KDC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             ......................... cmedia.local passed test LocatorCheck
          Starting test: FsmoCheck
             GC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             PDC Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             KDC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             ......................... cmedia.local passed test FsmoCheck
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
             provided.
             ......................... cmedia.local passed test Intersite

  • I work for a teaching hospital. We are using groups of 20 to 30 iPads for access to patient electronic records, video conferencing software, and other, HIPPA compliant apps. I need to be able to access the iPads to shut down and erase in case of loss.

    I work for a teaching hospital. I have started a program to place Physicians and key support personnel on iPads for electonic medical records, video conferencing software, and other HIPPA compliant issue. I have a need to have one central program that can push out updates, other information, but most importantly, can erase the iPad in cases of loss or stolen. Can anyone direct me to such software.
    Thanks,
    Wayne Hodges

    The Mac mini does have somewhat powerful specs at top end.
    Mac mini with OS X Server features a 2.3GHz quad-core Intel Core i7 processor that delivers incredible speed and performance, thanks to innovations like Turbo Boost 2.0, Hyper-Threading, and an integrated memory controller. Add in 6MB of L3 cache, and you’ll find that Mac mini with OS X Server is packed with power.
    http://www.apple.com/mac-mini/server/
    Here is  a list of  mdm's:
    MDMs
    Airwatch, Meraki, MobileIron, OS X Server, or Zenprise
    Airwatch
      http://www.air-watch.com/
    Meraki -- A free MDM   [ expect lots of email and phone calls about upgrades ]
      http://www.meraki.com/products/systems-manager/
      https://discussions.apple.com/thread/4067210?tstart=0
      Good howto by Sergio Sosa.
      https://discussions.apple.com/thread/2594001?start=15&tstart=0
    MobileIron
      http://www.mobileiron.com/
    Zenprise
      http://www.zenprise.com/

  • Creating SRV and CNAME records for Lync

    Our domain is hosted at Verio/Rapidsite.  The Zone File for the site has different columns than those identified in the setup information for Lync, so I am not sure how to set up the DNS changes to get Lync working.  The fields to be populated
    at Verio are Name, Ttl, Class, Type and Spec.  Our domain name is intergraphic.com.
    How do I apply the necessary information in this situation?

    Hi kristikay,
    Agree with Ben, you’d better consult Verio for support.
    Verio do not support SRV, so you can’t set up it in GUI, it only can be set up in your zone file.
    In addition, if possible you can move your DNS name to GoDaddy.
    A similar case for your reference.
    https://social.technet.microsoft.com/Forums/lync/en-US/8b41151b-ce4a-495e-9c93-f375796ca201/web-hosting-dns-limitations-no-srv-records
    Best regards,
    Eric

  • DNS (srv record missing for PDC)

    Hi,
    in our company we have a domain with 4 domain controller (all are Windows Server 2008 with domain functional level 2003).
    In the DNS, under _msdcs.OURDOMAIN.priv -> _tcp there are only the SRV _ldap record related to 3 domain controller; there isn't the record related to domain controller that holds the PDC role.
    From some months we have also issues about GPOs replicas between domain controller.
    It makes sense to create the missing record ? There may be a valid reason because it is not present ?
    Thank you.

     Hi,
    Did the PDC host the DNS role at the same time? If yes, please make sure that you have enabled secure dynamic updates on the DNS server. You can stop and restart
    DNS server by running the command below at the command prompt:
    net stop dns
    net start dns
    On the PDC, please stop and then restart the Netlogon service by running the commands below to see if the SRV record is created in the DNS server:
    Net stop netlogon
    Net start netlogon
    If the above solution is not helpful, please try to
    manually enter the SRV records from Netlogon.dns file in \Windows\System32\Config or create on the DNS console.
    Best regards,
    Susie

  • KMS SRV record in DNS

    Hi
    I have been doing an audit of our DNS zones and notice that some or other user has must have mistakenly registered their desktop as a kms host, since I see a DNS SRV record pointing to their pc on port 1688.
    This has caused problems for us so much so that we now activate using another kms host that is not part of our domain. my question is this: can I go into dns and simply manually edit this incorrect SRV record to reflect the correct dns name of the working
    kms host server?

    Hi,
    Do you mean that you still cannot find out the host according to the record?
    As a workaround, we can disable KMS host from publishing SRV record by creating a registry key via GPO. Even if someone configure a KMS host in your
    environment, DNS record will not be published. Remember not to apply to your real KMS host.
    Edit the GPO with the following:
    Computer Configuration>Preferences>Windows Settings>Registry
    Create a new
    DWORD value called
    DisableDnsPublishing in the registry, and set its value to
    1. This value is at
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform in the registry. To re-enable the default behavior for publishing of KMS SRV records to DNS,
    set the value to 0.
    Hope this helps.

  • Serious bug: call set-up problem in case of several DNS SRV records

    Hello Cisco,
    We have a MCU that consists of two servers in cluster. We have SIP SRV DNS records that point to both servers with equal priority and weight.
    All applications work nice with such setup, except from Free Jabber. Jabber is unable to set up the connection most of the time. One time the connection is successful and 5, maybe even 10 times it is unsuccessful.
    For testing, we removed SIP DNS records pointing to one server. This way Jabber works much better. There are some cases when the call set up fails but in most cases it works.
    Looking the logs of the MCU, we can see three different ways, how call set-up may fail. It is probably unreasonable describe the details in this forum message. Anyway, it seems to be sure that in case there SIP SRV records point to one server then Jabber is able to connect the MCU, in case the records point to two servers equally then Jabber is pricnipally unable to connect the MCU. This bug should be fixed, IMHO.
    Btw, what record does Jabber follow, is it _sips._tcp or _sip._tls?
    Greetings and thank you in advance,
    Marko Laurits

    Hello Cisco,
    We have a MCU that consists of two servers in cluster. We have SIP SRV DNS records that point to both servers with equal priority and weight.
    All applications work nice with such setup, except from Free Jabber. Jabber is unable to set up the connection most of the time. One time the connection is successful and 5, maybe even 10 times it is unsuccessful.
    For testing, we removed SIP DNS records pointing to one server. This way Jabber works much better. There are some cases when the call set up fails but in most cases it works.
    Looking the logs of the MCU, we can see three different ways, how call set-up may fail. It is probably unreasonable describe the details in this forum message. Anyway, it seems to be sure that in case there SIP SRV records point to one server then Jabber is able to connect the MCU, in case the records point to two servers equally then Jabber is pricnipally unable to connect the MCU. This bug should be fixed, IMHO.
    Btw, what record does Jabber follow, is it _sips._tcp or _sip._tls?
    Greetings and thank you in advance,
    Marko Laurits

  • Can I use a MIDI keyboard as an input device for a software instrument?

    I have a Casio CTK-2100 that I am currently playing around with in Logic Pro 9. It can record and playback the different instruments fine using MIDI tracks. But I was wondering if it is possible to use the keyboard as an input device for a software instrument instead of the "Step Input Keyboard".
    Is it? If so, how do I set it up?

    Yes, the terminology can be a bear, many, many years ago when I started using Logic the manuals were written completely by the programmers, while they were quite humorous in places the were also really hard to understand so I learned/realized.. you can't really do anything so wrong it's going to destroy your computer so why not go ahead and experiment. I learned the basics of Logic without a manual, months later when I went back to find some some details I could figure out the manual made a lot more sense.
    Logic has been somewhat Appleized but it's not really an Apple program, it was purchased almost as developed as it is now... a lot of the additions a fluff to make it easier to understand for new users while at the same time there are some real improvements.
    This is personal opinion: With all of the forums/online tutorials...etc...etc. It seems users are learning (but not understanding) the same things, plus everyone wants to use it right away so nobody takes a deep breath and investigates on their own. Logic is a deep, deep program, while learning don't be afraid to go off on a tangent and explore the program without any other input, it can actually be inspirational. One other thing good about the manual or "Online Help", in looking up a function you will invariably come across a related concept that will provide further insight.
    And..... have fun.

  • Lync 2010 client and SRV record

    When Lync 2010 was originally set up in our environment, we included our login domain which is a .local as a SIP domain but everyone uses our additional SIP domain which is a .org.
    In our internal DNS, we have SRV records under both domains. Question is if a Lync 2010 client is doing autodiscover and their SIP domain is the .org, will the client look at the SRV record in the .local domain? I don't think this SRV record was ever used
    even though its the users login domain, its not their SIP domain.

    You're right, the SRV records that belongs to your .local domain are not used by the lync client for a user that hs a .org sip domain sign-in address, so as you are saying if all the users are configured with a .org sip domain that means these SRV records
    were never used, and you can safely remove them.
    Regards,
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • DNS won't resolve SRV records with recursion disabled

    I have DNS installed on a Windows Server 2008 R2 server.  I have a standard zone created (no AD integration).  I have recursion disabled.  When I use NSLookup to lookup any of the A records or CName Records the results are returned as
    expected.  However, if I attempt to lookup any SRV or MX Records, the list of root hints are returned (which is what I would expect if I was attempting to lookup a domain not hosted on this server).  Now I enable recursion and run the same exact
    commands and I get the results I'm expecting.
    I'm stumped.....
    DB

    Reader's digest version:  Putting a period at the end of my record, resolved the issue.  This seems to be a difference between Windows 2003 and Windows 2008R2
    Long version:
    Thanks for the debug tip.  That confirms the issue.  So to backup a little, I had a Windows 2003 box running DNS.  I planned on decommissioning this box; therefore, I stood up the second server, made a secondary DNS zone, once all records
    transferred, I flipped the primary and secondary roles.
    The real problem is this zone cannot find any of the TXT records such as SRV and MX.  When I run NSLookup with recursion disabled, my results are:
        HEADER:
            opcode = QUERY, id = 18, rcode = NOERROR
            header flags:  response, want recursion
            questions = 1,  answers = 0,  authority records = 13,  additional = 3
    That makes perfect sense why recursion is working.  If I run the same results on the secondary DNS server (the original server) the results are expected:
        HEADER:
            opcode = QUERY, id = 20, rcode = NOERROR
            header flags:  response, auth. answer, want recursion, recursion avail.
            questions = 1,  answers = 4,  authority records = 0,  additional = 4
    SO THE REAL QUESTION is why can't the new server find these records, especially since it's a copy of the zone from the old server.  I flipped the servers back, deleted the DNS zone (and files) on the new server, restarted DNS service, created the zone
    again, and allowed the content to copy over from the old server and I STILL get the same results.
    The last thing I did was created a new SRV record on the new server and performed another NSLookup, but still get the same results.
    So then I remembered
    MuhammadUmar's post about putting a period at the end of my nslookup command.  I honestly didn't that that was going to change the results, but BAM.  I was wrong.  When I put in the request with a period at the end of the record, I get the
    results I'm expecting.
    Thanks all for helping me on this one!
    DB

Maybe you are looking for

  • Unwanted Snippets appear in Webhelp output

    When producing Webhelp output, I've been having an out-of-date snippet appear in my document.  I use a common snippet in several projects, and in some of the projects, the snippet appears twice in the output when it's not supposed to.  I've modified

  • Is it safe to reload your OS using BlackBerry Device Software? (9300 curve)

    I'm planning to Reload my OS 6 using BB Device Software to fix the battery problem. Will this be safe? Or is this the proper way on reloading the OS. here is the link I want to perform : KB11320 - How to perform a clean reload of the BlackBerry Devic

  • Upgraded to 5.5-- GPU Hack now doesn't work

    With Premiere CS5 (Master Suite) the GPU hack outlined here worked great with my NVidia 470M card installed in my Sager 7280. But that changed with the 5.5 Master Suite upgrade. To start with, I was unable-- after 5 tries-- to install 5.5 without get

  • How can I get missing files for Classroom in a Book?

    I bought Classroom in a Book for Premiere Pro CS 5 and some of the lessons are missing the audio/video that I need to complete these lessons. I know this isn't directly an Adobe problem, but I'd appreciate it if someone knew a place online I could go

  • Significance of Preliminary cost estimate,

    Hi experts, My clinet is using REM scenairo and in REM profile we have maintained "Backflush using standard cost estimate". My question is in this case what is the significance of preliminary cost estimate(PCE)? and I would able to confirm (MFBF) wit