I currently have one .local address (Bonjour) pointing to my mac in my intranet, mbp.local, configured in system preferences with the computer name. I use this to send my boss links to demos on my local server (he sits in a chair behind me : >).
I'd like to be able to create new .local addresses to send different demos to my boss (demo1.local, demo2.local, etc) so that I can switch to different working copies to do other work while the demos are still live.
I'd know how to setup Apache to route these requests to the right places, but am unsure if it's possible to make new addresses that point to my mac (I think this has to do with multicasting?).
I have a dynamic IP in my intranet but would be able to setup a static IP if required.
Are you talking about web site demos? I'm not sure I understand the problem. If they're web sites, I'm sure you already know you can simply use a single address with different urls, eg, http://mbp.local/demo1, http://mbp.local/demo2, etc. If it is something else entirely, you can use the Mac's local host file to point multiple fqdns to a single IP address on your local network, but it would be best to have a static IP. Alternatively, you could edit your DNS or WINS server to do the address translation.
I haven't done this myself, but I wonder if you could use what's documented here to start. The difference would be that you'll send your boss links to http://demo1.mbp.local and so on.
I found more about this on this thread on SuperUser.
Related
I've installed Alfresco CE in a Windows 7 machine (which is not ideal, but I have to deal with it). I can access my Alfresco share from inside the network:
192.168.2.252:8080/share
As far as I know, I can access it from outside the network using a dns service like no-ip.org, which gives me something like:
example.no-ip.org:8080/share
What I'm trying to do is to get something like:
mycustomdomain.com/share/ (removing the /share/ would be great too)
I've been reading a lot, but I'm not sure what to do. I read something about setting up DNS on my machine, but I don't know how to point the domain to the Alfresco share. Any suggestions?
Ip which you have shared is internal IP.You need to have one external IP.Which can be accessed outside network.
Below file will help you in URL redirection.If you want to remove share , you may also do that by configuration in below file.
tomcat\webapps\share\WEB-INF\urlrewrite.xml
I have a slight problem bit of the back story. recently ive been trying to test out univention which is a linux distribution with the goal of being able to replace Microsoft active directory.
I tested it locally and all went reasonably well after a few minor issues i then decided to test it remotely as the company wants to allow remote users to access this so i used myhyve.com to host it and its now been setup successfully and works reasonably well.
however
my main problem is DNS based as when trying to connect to the domain the only way windows will recognize it is by editing the network adapter and setting ip v4 dns server address to the ip address of the server hosting the univention active directory replacement. although this does allow every thing to work its not ideal and dns look up on the internet are considerably longer. i was wondering if any one had any ideas or have done something similar and encountered this problems before and know a work around. i want to avoid setting up a vpn if possible.
after initially registering the computer on the domain i am able to remove the dns server address and just use a couple of amendments to the HOST file to keep it running but this still leads to having issues connecting to the domain controller sometimes and is not ideal. any ideas and suggestions would be greatly received.
.Michael
For the HOST entries, the most likely issue is, that there are several service records a computer in the domain needs. I'm not sure, whether these can be provided via the HOST file or not but you'll definitely have authentication issues if they are missing. To see the records your domain is using issue the following commands on the UCS system.
/usr/share/univention-samba4/scripts/check_essential_samba4_dns_records.sh
For the slow resolution of the DNS records there are several points where you could start looking. My first test would be whether or not you are using a forwarder for the web DNS requests and whether or not the forwarder is having a decent speed. To check if you are using one, type
ucr search dns/forwarder
If you get a valid IP for either of the UCR Variables, dns/forwarder1, dns/forwarder2 or dns/forwarder3, you are forwarding your DNS requests to a different Server. If all of them are empty or not valid IPs then your server is doing the resolution itself.
Not using a forwarder is often slow, as the DNS servers caching is optimized for the AD operations, like the round robin load balancing. Likewise a number of ISPs require you to use a forwarder to minimize the DNS traffic. You can simply define a forwarder using ucr, I use Google on IPv4 for the example
ucr set dns/forwarder1='8.8.8.8'
The other scenario might be a slow forwarder. To check it try to query the forwarder directly using the following command
dig univention.com #(ucr get dns/forwarder1)
If it takes long, then there is nothing the UCS server can do, you'll simply have to choose a different forwarder from the ucr command above.
If neither of the above helps, the next step would be to check whether there are error messages for the named daemon in the syslog file. Normally these come when you are trying to manually remove software or if the firewall configuration got changed.
Kevin
Sponsored post, as I work for Univention North America, Inc.
I have set up a Bitnami GitLab stack as a running virtual machine instance using VMWare Workstation on my personal dedicated Windows server (host) running out of my home office. My dedicated Windows server host has a publicly visible static IP address.
I have successfully gained public access to the GitLab application running as guest by setting up port forwarding within VMWare Workstation's Virtual Network Editor (using NAT translation, not bridging). I am able to access the GitLab web interface from any internet-connected computer just by typing the static IP (including my chosen port).
I have also successfully set up two Git repositories in the running GitLab instance.
Sending email needs to be enabled, requiring a modification of a settings file, and this worked straightforwardly (here is a link that explains how to set up SMTP properly).
Before inviting new users, I wanted to test the functionality by inviting myself first (using a secondary email address).
When inviting a user, an invitation/confirmation email is sent to that user that provides a link to login to the GitLab instance. However, I find that the URL provided in the invitation email is the local network IP address (i.e., 192.168.44.129) rather than the publicly visible static IP address.
I do not see any settings in the GitLab web interface itself to change the host IP included with email invitations, so I assume I need to change a setting in a configuration file somewhere. But I have no idea if this should be a GitLab setting, an Nginx setting, a RoR setting, or some other setting; and what the setting / setting file is.
The best links I can find about this (here, here, and here) do not seem to lead me to sufficient clarity to take an efficient guess as to what to do.
How do I change the URL (host IP) that is provided in invitation emails to new users via GitLab from the local network IP address to a globally-visible (static) IP address?
Two hints pointed the way for me, and once I did resolve the issue (as I am about to describe), I found the details laid out in the deceptively named subsection of the Bitnami GitLab stack official documentation.
The first hint was to be found in a not-very-highly-upvoted answer here (in comparison with other answers and the accepted answer, some of which had many more upvotes). The setting for the host IP and port used in the GitLab account invitation emails is to be found in the gitlab.yml file (as of today, the full path of this file on the VM stack (and probably other) installations is /opt/bitnami/apps/gitlab/htdocs/config/gitlab.yml; see the host and port settings, as well as other overall useful settings). (I'm not experienced with the Rails universe, and using the .yml settings file is a touch, apparently, of the way Rails apps in general do things, if I understand correctly.)
The above step does succeed - but only until the server is restarted. Unfortunately, when the server is restarted, the host setting is overwritten with whatever is present in ifconfig as the IP address (the port entry remains the same as whatever you enter).
The second hint was how to resolve this problem; I found it here. There is a special script in the init.d folder whose specific purpose is just to reset the host parameter in this (and perhaps other?) .yml settings files. (What a wonderful "convenience" in my scenario.) Simply commenting out the single line exec /opt/bitnami/apps/gitlab/bnconfig --machine_hostname ... in this file (by adding a # at the front of the line) resolved the problem.
Once both of the above changes were made, the problem was resolved. GitLab invitation emails successfully include the desired static IP address (and port) of the server, even through server restarts.
As I mentioned above, once I resolved the problem, I then found that the answer to this question was already laid out in the official Bitnami GitLab documentation (note: both hint #1 and hint #2, from above, are tucked away in this same subsection of the documentation - one after the other - they're not prominent; they don't stand out very well; they come across as secondary details upon first reading, I think; the formatting does not draw attention to the file name and path, which would be helpful, I think; and the subsection name in which they are present does not particularly make it clear that this would be the correct subsection to look at, except in retrospect, in my opinion).
ADDENDUM: For anyone who finds it useful, there's an added detail required to get email working from your own personal server with GitLab - I made only a brief passing mention of this in the question, because I had already done it.
But for completeness for future visitors, I should mention that you need to set up SMTP properly on your GitLab instance by making a modification to a file named production.rb (the full path as of today is /opt/bitnami/apps/gitlab/htdocs/config/environments/production.rb). Specifically, as is also to be found in the official Bitnami GitLab documentation, you must add a config.action_mailer.smtp_settings {...} block and add/uncomment a few other settings in order to be able to send emails from your running GitLab instance.
Our client currently has a website on their own domain: we are in the process of setting up their new site on a new server, with the same domain name.
Originally we started work on a subdomain that they could access when need be. As time came closer we pushed the work to the actual domain (on the new server) and continued to make changes (by adding a line to our hosts file to ensure we were looking at the new server).
The client wants to see the site as it stands today, before switching the DNS to point to the new server. While we could copy everything back to the original subdomain that is not as easy as we first hoped, as unfortunately there's a few too many links and references to files using the domain name (as opposed to just using relative paths).
One other thing: the code auto-redirects back to the 'proper' domain if it's not currently being used (it's a Magento install) and this stops the possibility of pointing the subdomain document root to the current directory (as the first thing that will happen is that it will see that we're using the subdomain, and will push the client to the original domain).
What are our options? I know that we could get them to change their hosts file, but I'm hoping for something a little less 'techy' for the client.
Is there any proxy server out there that we can use, specifically using our own DNS settings, maybe, or is there some Windows client side application that they could install to make it a bit simpler?
It would be pretty darn simple to write a program — in pretty much any language — which would change the hosts file for your clients. All they'd need to do is run the program.
Alternately (this is more work, and not necessarily any more benefit) you could set up a DNS server on the subnet, and configure the web server to use that DNS server. I really don't see this being any easier than just (somehow) modifying the hosts file, though.
I wrote my own proxy server for exactly this purpose: http://chiselapp.com/user/evilotto/repository/web-tools/wiki?name=hr-proxy
The standalone executable is not there, but it can be bundled into a starpack fairly easily. It it only a proxy tho, and does not do things like change the user's system proxy settings (meaning the user would need to change that themself through Internet Options, etc)
i have a linux client which uses pppoe to connect to the internet and
everytime this client comes online I wanna bind his ipadress to a subdomain.
dyndns is not an option due to their TTL.
It looks like i have to setup my own nameserver on my root server to accomplish this task because I cannot create the keys needed to run an nsupdate on the client with a provider nameserver... am I correct?
If so is there a good Howto for setting up a bind server for this specific task?
I havent ever maintained pppoe but if it uses dhcp to provide the ip address to the client, you could do updates from the dhcp to the dns.
Instructions on how to do this for debian here: http://www.debian-administration.org/article/Configuring_Dynamic_DNS__DHCP_on_Debian_Stable
Do not thou that you can adapt these to other distros too. You can find the same software atleast on fedora and ubuntu, difference is only how you install the required software.
One posibility is to set their machine to register with somebody like DynDNS. They have all the software you need to automatically notify them when they come online/go offline. This will give them a domain name of something like whatever.homelinux.org (it does not really matter). You then put static CNAME entries in your DNS to point your nice domain names eg southern.company.com to point to whatever.homelinux.org.
When they come online the domain will start to resolve and stop when they go off line since DynDNS have low TTL for this very reason. You can use large TTL in your zone file since the CNAMEs will not change.
Well dont you just need to create an A-Record for this IP on your DNS Server?
If your domain is 'google.com' and you wanted your host to be called 'server1'. Create an A-Record for 'server1' and point it to your machines IP.
Unless I am misunderstanding what you are asking for help with.