tag:blogger.com,1999:blog-330512563102289335.post6607404337305103415..comments2024-03-13T00:57:41.117-07:00Comments on TsooRaD: 1008;reason=Unable to resolve DNS SRV recordtsooradhttp://www.blogger.com/profile/17928837963455872673noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-330512563102289335.post-5476409573889097412017-03-08T16:03:19.598-08:002017-03-08T16:03:19.598-08:00@zyphen
"But I do know what fixed this issue ...@zyphen<br />"But I do know what fixed this issue – the federation SRV record being added to the internal DNS zone and modification of the Edge Server host files so that they can find the SRV target by IP."<br /><br />So, create a federation srv record internally for the edge server to find. And if that SRV has a target of xyz@domain.com, and you need that for something else internally, you can go to the edge server, and put an entry into the host file for the target of the federation SRV record. When the Edge server looks up the federation SRV record, it will also try to resolve the target - and when it finds that target FQDN in its host file, it will use it.<br />So you give the edge server access edge out as your FQDN for target of the federation SRV, and the host file gets the PUBLIC access edge IP = FQDFN and problem solved.<br /><br />Clear as mud?<br /><br /><br />tsooradhttps://www.blogger.com/profile/17928837963455872673noreply@blogger.comtag:blogger.com,1999:blog-330512563102289335.post-10279045870709374752017-03-07T15:13:13.166-08:002017-03-07T15:13:13.166-08:00Hey what do you mean by "And then modified th...Hey what do you mean by "And then modified the host file on each Edge server to have the public IP for themselves"<br /><br />we are having the exact same issueZyphenhttps://www.blogger.com/profile/15872151245968145752noreply@blogger.com