RPC SERVER UNAVAILABLE AND NAMESERVER PORT 42

I ran this command on my Domain COntroller server

dcdiag /e /v /f:c:\dcdiag.txt

all tests passed except for the ones below.

Starting test: DFSREvent

         The DFS Replication Event Log.
         The event log DFS Replication on server serverB.COMPANY.local could not be queried, error 0x6ba "The RPC server is unavailable."

         ......................... serverB failed test DFSREvent

      Starting test: SysVolCheck

         * The File Replication Service SYSVOL ready test
         File Replication Service's SYSVOL is ready
         ......................... serverB passed test SysVolCheck

      Starting test: KccEvent

         * The KCC Event log test
         The event log Directory Service on server serverB.COMPANY.local could not be queried, error 0x6ba "The RPC server is unavailable."

         ......................... serverB failed test KccEvent


------------portqry ui ------------------------------------------------------------------
I also ran the portqry tool and this is the output


....................

.....supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 6
forestFunctionality: 6
domainControllerFunctionality: 6


======== End of LDAP query response ========

UDP port 389 is LISTENING

portqry.exe -n serverb -e 389 -p BOTH exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n serverb -e 636 -p TCP ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 636 (ldaps service): LISTENING
portqry.exe -n serverb -e 636 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n serverb -e 3268 -p TCP ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 3268 (msft-gc service): LISTENING

Using ephemeral source port
Sending LDAP query to TCP port 3268...

LDAP query response:


currentdate: 05/29/2015 17:41:41 (unadjusted GMT)
subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=company,DC=local
dsServiceName: CN=NTDS Settings,CN=serverb,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=company,DC=local
namingContexts: DC=company,DC=local
defaultNamingContext: DC=company,DC=local
schemaNamingContext: CN=Schema,CN=Configuration,DC=company,DC=local
configurationNamingContext: CN=Configuration,DC=company,DC=local
rootDomainNamingContext: DC=company,DC=local
supportedControl: 1.2.840.113556.1.4.319
supportedLDAPVersion: 3
supportedLDAPPolicies: MaxPoolThreads
highestCommittedUSN: 35641
supportedSASLMechanisms: GSSAPI
dnsHostName: serverb.company.local
ldapServiceName: company.local:serverb$@company.LOCAL
serverName: CN=serverb,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=company,DC=local
supportedCapabilities: 1.2.840.113556.1.4.800
isSynchronized: TRUE
isGlobalCatalogReady: TRUE
domainFunctionality: 6
forestFunctionality: 6
domainControllerFunctionality: 6


======== End of LDAP query response ========
portqry.exe -n serverb -e 3268 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n serverb -e 3269 -p TCP ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 3269 (msft-gc-ssl service): LISTENING
portqry.exe -n serverb -e 3269 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n serverb -e 53 -p BOTH ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 53 (domain service): LISTENING

UDP port 53 (domain service): LISTENING
portqry.exe -n serverb -e 53 -p BOTH exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n serverb -e 88 -p BOTH ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 88 (kerberos service): LISTENING

UDP port 88 (kerberos service): LISTENING or FILTERED
portqry.exe -n serverb -e 88 -p BOTH exits with return code 0x00000002.
=============================================

 Starting portqry.exe -n serverb -e 445 -p TCP ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 445 (microsoft-ds service): LISTENING
portqry.exe -n serverb -e 445 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n serverb -e 137 -p UDP ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...


Name resolved to 10.X.X.X

querying...

UDP port 137 (netbios-ns service): LISTENING or FILTERED

Using ephemeral source port
Attempting NETBIOS adapter status query to UDP port 137...

Server's response: MAC address 000c299db6c5
UDP port: LISTENING
portqry.exe -n serverb -e 137 -p UDP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n serverb -e 138 -p UDP ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...


Name resolved to 10.X.X.X

querying...

UDP port 138 (netbios-dgm service): LISTENING or FILTERED
portqry.exe -n serverb -e 138 -p UDP exits with return code 0x00000002.
=============================================

 Starting portqry.exe -n serverb -e 139 -p TCP ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 139 (netbios-ssn service): LISTENING
portqry.exe -n serverb -e 139 -p TCP exits with return code 0x00000000.
=============================================

 Starting portqry.exe -n serverb -e 42 -p TCP ...


Querying target system called:

 serverb

Attempting to resolve name to IP address...

Name resolved to 10.X.X.X

querying...

TCP port 42 (nameserver service): FILTERED
portqry.exe -n serverb -e 42 -p TCP exits with return code 0x00000002.

-----------------------------------------------------------------------------------------

The last error - port 42 TCP - is that something to be alarmed about.
DO i need to manually open port 42 both inbound and outbound on both the domain controllers

ENVIRONMENT
I have two domain controllers, windows 2012 r2.
no dfs name spaces

Running this command also shows no errors
repadmin /showrepl



Any help appreciated