A Unified Communication Blog
Get Adobe Flash player

When running the validation wizard on the Access Edge server, you get this error:

Problem:

DNS Resolution failure: No DNS SRV records corresponding to _sipfederationtls._tcp.domain.com were found for this domainSuggested Resolution: Verify that the domain name is correct and that the DNS SRV record _sipfederationtls._tcp.domain.com exists for this domain.

Warning[0x43FC200C] Not all checks were successful

Solution:

Verify the external DNS settings (http://it-proknowledge.blogspot.com/2008/01/troubleshooting-ocs-federation.html)

If you are using internal DNS servers on the Access Edge server, the problem might be that the public DNS zone (Domain) is also owned by the internal DNS servers, and therefore the DNS lookup is done against the Internal DNS zone. Use the SRVLOOKUP tool (explained in the article in the link above) from a computer outside the network.

UPDATE:

Heres some steps to do when troubleshooting this problem.

1. From the Access Edge server, ping your external sip domain name (sip.domain.com). You should be able to resolve the name to an IP address. (ping response is not needed)

2. From the Access Edge server, use the SRVLOOKUP tool, explained in item 1, in the above linked articel. The response from the SRVLOOKUP tool, should be you sip domain (sip.domain.com)

Both these test shoul be positive. If not, there is a DNS issue.

I have found that best practise for DNS on Access Edge servers, is to build a seperate DNS server:

  1. Install DNS Server from Add- Remove Windows Components
  2. Configure the DNS server to use root hints (this should be default)
  3. Configure the firewall protecting the Access Edge server from the Internet, to allow DNS outbound
  4. Verify connectivity by using the tool in the DNS Server MMC snap-in
  5. Configure the servers NIC to use the new DNS server as primary DNS

This way, you should be able to have clean DNS resolution on the Access Edge server.

Please let me know if you have any relevant issues

Regards,
Rasmus

2 Responses to DNS Resolution failure [0x43FC200C]

  • Hi,

    I have this warning when I validate my Edge Server.
    I would like to read the full article, but it seems that its end is missing.

    Best Regards,

    Nicolas

  • Hi Nicolas

    If, …….

    I liked that one! Thanks for posting a comment about it!

    I have updated the article, so it should be more clear. Please post if you have any other relevant problem that is not described here.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Search

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 71 other subscribers

Follow me on Twitter