Answers: <p>As I understand it you need to establish a network service (I.e, compose file), though if you are working with a docker file (e.g, ver. docker 1.x &lt; 2) you typically issue a command or execute a script. In either case, I’ll need to create a new network service and bridge ports (I.e, expose port) to make them accessible:</p>
  
  <p>A &lt;-> B -> C </p>
  
  <p>Check out the documentation: </p>
  
  <p><a href="https://docs.docker.com/network/" rel="nofollow noreferrer">https://docs.docker.com/network/</a></p>
  
  <p>Hope that helped.</p>
  
Answers: CC BY-SA 4.0
Answers: 2018-12-10T22:13:21.610Z
Answers: @AigoLamda not really it did not. I got A and B to work using DNS Proxy Server container. I'm trying to get C which is a local network with A but not B to see B, however, I need to access it via www.domain.url and not ip:port
Answers: Kendall
Answers: CC BY-SA 4.0
Answers: 2018-12-11T14:28:48.827Z
Answers: Sorry, if it wasn't much help. I also found [link](https://docs.docker.com/datacenter/ucp/2.1/guides/user/services/use-domain-names-to-access-services/) maybe this would help. If you are trying to access a container via domain name using a container service. The examples a bit crud but it can be extrapolated.
Answers: TheoNeUpKID
Answers: CC BY-SA 4.0
Answers: 2018-12-10T06:07:57.810Z
Answers: 2018-12-10T06:07:57.810Z
Answers: TheoNeUpKID
Body: <p>hey guys I have a docker container A with a domain name attached to it on a host B with a domain name attached to it as well.....how can I access the said container A via A's domain name rather than an B's ip address or domain name from computer C on the host B's local network</p>
  
Tags: <docker><networking><dns>
Title: Accessing container by domain name
UserDisplayName: Kendall
ThreadText: # Accessing container by domain name
  
  (Asked by: username_0 on 2018-12-09)
  
  hey guys I have a docker container A with a domain name attached to it on a host B with a domain name attached to it as well.....how can I access the said container A via A's domain name rather than an B's ip address or domain name from computer C on the host B's local network
  
  **Tags:** docker, networking, dns
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-12-10. Score: 1
  
  As I understand it you need to establish a network service (I.e, compose file), though if you are working with a docker file (e.g, ver. docker 1.x < 2) you typically issue a command or execute a script. In either case, I’ll need to create a new network service and bridge ports (I.e, expose port) to make them accessible:
  
  A <-> B -> C
  
  Check out the documentation:
  
  <https://docs.docker.com/network/>
  
  Hope that helped.
  
  > **Comments:**
  > **username_0**: @AigoLamda not really it did not. I got A and B to work using DNS Proxy Server container. I'm trying to get C which is a local network with A but not B to see B, however, I need to access it via www.domain.url and not ip:port  
  > **username_1**: Sorry, if it wasn't much help. I also found [link](https://docs.docker.com/datacenter/ucp/2.1/guides/user/services/use-domain-names-to-access-services/) maybe this would help. If you are trying to access a container via domain name using a container service. The examples a bit crud but it can be extrapolated.  
  
  ---
  
  