Skip to main content
replaced http://serverfault.com/ with https://serverfault.com/
Source Link

DNS only translates names into IP addresses and is oblivious to any port numbers.

However, you can use Apache as a reverse proxy to make the content accessible at git.domain.com by editing the virtual host file. I believe thisthis answer on Server Fault shows one method of how to do this that should work well for you.

DNS only translates names into IP addresses and is oblivious to any port numbers.

However, you can use Apache as a reverse proxy to make the content accessible at git.domain.com by editing the virtual host file. I believe this answer on Server Fault shows one method of how to do this that should work well for you.

DNS only translates names into IP addresses and is oblivious to any port numbers.

However, you can use Apache as a reverse proxy to make the content accessible at git.domain.com by editing the virtual host file. I believe this answer on Server Fault shows one method of how to do this that should work well for you.

Edited for clarity and formatting.
Source Link
dan
  • 15.2k
  • 11
  • 45
  • 52

DNS only translates names into IP addresses and is oblivious to any portsport numbers. But

However, you can use Apache as a reverse proxy to make the content accessible at git.domain.comgit.domain.com by editing the virtual host file.

  I believe this answersthis answer on Server Fault shows you exactly aone method whichof how to do this that should work well for you :) - http://serverfault.com/a/85115/191794.

DNS only translates names into IP addresses and is oblivious to any ports. But you can use Apache as a reverse proxy to make the content accessible at git.domain.com by editing the virtual host file.

  I believe this answers shows you exactly a method which should work for you :) - http://serverfault.com/a/85115/191794

DNS only translates names into IP addresses and is oblivious to any port numbers.

However, you can use Apache as a reverse proxy to make the content accessible at git.domain.com by editing the virtual host file. I believe this answer on Server Fault shows one method of how to do this that should work well for you.

Source Link
Analog
  • 2.4k
  • 17
  • 29

DNS only translates names into IP addresses and is oblivious to any ports. But you can use Apache as a reverse proxy to make the content accessible at git.domain.com by editing the virtual host file.

I believe this answers shows you exactly a method which should work for you :) - http://serverfault.com/a/85115/191794