Issues accessing SRV programatically

[jogster]

I have got the service working on my cluster. I can see it register and deregister SRV records in the console for my Route53 servicediscovery.internal zone...

But I cannot get dig working to view the SRV records. Additionally I wrapped the simple go function (example access) in a main and did not get any data back.

If I insert a manual 'A' record using the aws cli I can see it using dig.

I assume there is something fundamental that I am missing? I am not using the cloudformation template but an existing cluster I had configured...

This is the command I am using:

dig <svc_name>.servicediscovery.internal SRV

How is everyone accessing the SRV record?

[ruslantalpa]

on one of the ECS cluster nodes, this works for me
dig +short srv <svc_name>.servicediscovery.internal

where are you executing dig?

[javierros]

Perhaps you're doing a query for an A record instead of a PTR record, can you try the command from ruslantalpa?

[jogster]

That was the command I was trying originally it didn’t work. I will setup the test system again and retry.

…

On 11 Oct 2017, at 13:42, Javier Ros ***@***.***> wrote: Perhaps you're doing a query for an A record instead of a PTR record, can you try the command from ruslantalpa? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFoUp8sKiwBhFHLWxjGbxmHM0cRu9mhks5srLeYgaJpZM4OoI5->.

[dickmao]

Did you perhaps have two clusters active each with their own hosted zone named servicediscovery.internal? The ecssd_agent code as written will only act on the first hosted zone it sees with that name, and this can result in dig not returning the srv record. At least that's what happened to me until I gave the hosted zones unique names.