I just set up a DirectAdmin server. What I'd like to accomplish is disabling http://example.com:2222 on certain websites. Is that possible?
Sorry but according this link it seems you can't do that!
If you point the domain to a dedicated IP then you can block access to 2222 on the IP with firewall.
There are no other options.
anyway if we assume you could do this other users also can access your directadmin with your IP address like this :
1.2.3.4:2222
I really don't know why you wanna do this but maybe changing your server port is good option..
Related
I started learning some website designing and I wonder how can I make my site adress look f. ex. like ender.com instead of IP address and port. I'm doing everything on my own computer, so I would really appreciate way, which will allow me to host a website on it. I'm a beginner, so I'd like to know if I'm even capable of doing this.
You need a domain name in which you're gonna host your website, in your case its ender.com, as you run your website from your own pc it shows your localhost and port instead of ender.com as you don't own that domain. Only way to show ender.com is that you buy that domain and host the website with that purchased domain.
Refer this for more info https://blog.resellerclub.com/how-to-host-a-domain-website-on-your-own/#:~:text=%20A%20few%20steps%20on%20how%20to%20host,may%20have%20issues%20here%20based%20on...%20More%20
I have a Linode server operating under a single IP Address. I access various websites via the single IP addresses in the following format: http://x.x.x.x/mysite1
Is it possible to access my individual websites, mysite1 etc, via names set in /etc/hosts?
In /etc/hosts I tried setting:
x.x.x.x dev.mysite
But, attempting to access my website via http://dev.mysite results in a webpage not found error.
Is what I'm trying to accomplish possible?
As long as you have made the /etc/hosts modification on the machine that is trying to access the website, then yes this is possible. Although you will also have to modify your Apache config so it knows which website to display when "dev.mysite" is requested. My Apache knowledge is rudimentary but I believe you want VirtualHost for this.
If you want other people to access the website without modifying their hosts file, you will need to buy a domain. For instance, if you buy xyz.com, you can put your sites under site1.xyz.com, site2.xyz.com and so on.
I believe Your /etc/hosts needs no change . dev.mysite already points to mysite.com which has an entry in /etc/hosts
You need to modify your web server (nginx / Apache)listening in port 80 to accept requests on dev.mysite
I have a computer running XAMPP on 192.168.1.X:80 and that port forwarded, along with a domain I can set nameservers and/or zone records on.
Security risks aside, how do I set the domain so I can go to mydomain.com and see my XAMPP server?
Edit: I can verify that my port forwarding works, I just need to be able to access it through my domain, not the 12.345.678.90:1234 address.
Excuse my bad english.
One of the ways is:
Visit http://www.noip.com and Sign in. There you'll get your Domain. You'll have to get location on the file 'host', modify your hosts file using this link http://www.rackspace.com/knowledge_center/article/how-do-i-modify-my-hosts-file
[www.dyndns.com] is a site which gives us internet service,
If I use their service and get a domain name with an i.p.
Their server will transfer the domain name to 1.2.3.4 when someone browse it.
what did they do at the back? how can they do this?
can I set up a server like that?
Refer to this link you will find you answer there.
http://computer.howstuffworks.com/dns2.htm
If you make you question clearer I could provide a better answer.
If you wish to create a local DNS on your system I would suggest you make alterations to your hosts file. Located at C:/Windows/System32/Drivers/etc in windows system.
The order in which DNS names are resolved is:
HOSTS configuration file
The DNS to which your computer is confugured
The HOSTS file has the highest priority so you could override the DNS server by configuring an IP in your HOSTS file.
I recently moved my website to a shared hosting solution at asmallorange.com, but I had to set my domain to use their provided nameservers in order for the site to properly resolve. I was determined to keep control of the domain's DNS but I could find no way to make my top level domain resolve to the shared location which was in the format of
server.asmallorange.com/~username
So I know I'm missing something here, my question is this:
What in their nameservers/DNS entry makes it possible for server.sharedhost.com/~username to serve as a top level domain? (ie. http://topleveldomain.com)
Nothing. DNS simply maps topleveldomain.com to server.sharedhost.com. It's the webserver which looks at the Host: topleveldomain.com header and knows that's equivalent to server.sharedhost.com/~username.
Nothing. They are having your domain name resolve to the same IP that server.asmallorange.com resolves to, but then they are making their web server aware of the domain name topleveldomain.com, and telling the webserver that it is the same as server.asmallorange.com/~username.
Virtual hosts aren't a DNS trick, they're an HTTP trick - the hostname requested is sent by the browser in a Host: field of every request.
apache has a "mod_user" which you can enable in your apache conf file. Using this and virtual hosts is how that is accomplished.
Virtual Hosts in Apache are how this is done.
However just because you set the DNS up to go "mydomain.com resolves to 1.2.3.4", which is their IP address, doesn't mean that you're giving up control of your domain name.