{"action":"created","issue":{"url":"https://api.github.com/repos/rancher/rancher/issues/3151","repository_url":"https://api.github.com/repos/rancher/rancher","labels_url":"https://api.github.com/repos/rancher/rancher/issues/3151/labels{/name}","comments_url":"https://api.github.com/repos/rancher/rancher/issues/3151/comments","events_url":"https://api.github.com/repos/rancher/rancher/issues/3151/events","html_url":"https://github.com/rancher/rancher/issues/3151","id":124407325,"number":3151,"title":"Subdomains and domains not resolving on public port 80","user":{"login":"Jdesk","id":9715064,"avatar_url":"https://avatars.githubusercontent.com/u/9715064?v=3","gravatar_id":"","url":"https://api.github.com/users/Jdesk","html_url":"https://github.com/Jdesk","followers_url":"https://api.github.com/users/Jdesk/followers","following_url":"https://api.github.com/users/Jdesk/following{/other_user}","gists_url":"https://api.github.com/users/Jdesk/gists{/gist_id}","starred_url":"https://api.github.com/users/Jdesk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Jdesk/subscriptions","organizations_url":"https://api.github.com/users/Jdesk/orgs","repos_url":"https://api.github.com/users/Jdesk/repos","events_url":"https://api.github.com/users/Jdesk/events{/privacy}","received_events_url":"https://api.github.com/users/Jdesk/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/rancher/rancher/labels/kind/question","name":"kind/question","color":"dddddd"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-12-30T22:24:22Z","updated_at":"2016-03-04T21:42:02Z","closed_at":"2016-03-04T21:42:02Z","body":"No matter what on compute nodes setup sub domains and domains will not resolve to app.foo.com:port. or app.foo.com.   If created via cli, is not an issue - however my situation is also unique.  \r\n\r\nI had a previously created nfs server setup using nfsv3 with the appropriate folders mountable however since this is basically just loopback storage even though it's on another server - it's cloud based, not on premise.  It should not matter when something is a public facing app.  obviously dbs don't go on public ports. We also used to be able to have the app on public port 80 and container port (usually using the port app is developed to listen on) and rancher would do the forwading.  \r\n\r\n Even using route53 (which I use) and in the past rancher had issues creating dns entries - now it doesn't which rocks (hate dns). However as needed if an app was done and we wanted to put it into our portfolio and want it on a pretty sub-permalink (sorry wordpress speaking) - Even port with subdomain is fine. \r\n\r\nIn previous version of rancher server - we could simply manually change the port to 80 in rancher and have it on a separate port inside the container - then point as many domains as we wanted at it. Put etcd plus kubernetes in the mix and it was a beatiful thing to say the least as even when rancher went down, the apps stayed up then we could add via cli to the rancher host.  \r\n\r\nNow apps will only resolve publicly to ip and port. eg 1.2.3.4:5678  I love how everything is coming along by the way - the features are actually making things too simple it feels - but hey that is fine - rather than typing - let's produce during deploy time.  However I know it's still beta - and there are bugs you want to know about.  "},"comment":{"url":"https://api.github.com/repos/rancher/rancher/issues/comments/192480516","html_url":"https://github.com/rancher/rancher/issues/3151#issuecomment-192480516","issue_url":"https://api.github.com/repos/rancher/rancher/issues/3151","id":192480516,"user":{"login":"deniseschannon","id":11410997,"avatar_url":"https://avatars.githubusercontent.com/u/11410997?v=3","gravatar_id":"","url":"https://api.github.com/users/deniseschannon","html_url":"https://github.com/deniseschannon","followers_url":"https://api.github.com/users/deniseschannon/followers","following_url":"https://api.github.com/users/deniseschannon/following{/other_user}","gists_url":"https://api.github.com/users/deniseschannon/gists{/gist_id}","starred_url":"https://api.github.com/users/deniseschannon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/deniseschannon/subscriptions","organizations_url":"https://api.github.com/users/deniseschannon/orgs","repos_url":"https://api.github.com/users/deniseschannon/repos","events_url":"https://api.github.com/users/deniseschannon/events{/privacy}","received_events_url":"https://api.github.com/users/deniseschannon/received_events","type":"User","site_admin":false},"created_at":"2016-03-04T21:42:02Z","updated_at":"2016-03-04T21:42:02Z","body":"@Jdesk \r\n\r\nPlease re-open with the requested docker-compose.yml of your stack and your desired behavior. "}}