how do you take a website off of the internet? i have been tasked by my local golf club to remove there old website but im not sure how to do it.
i know the ip address but i dont know where to start to take the site down.
Two suggestions:
Probably the quickest and easiest is to change your dns. You will need to know the dns provider so you can change the address it points to.
If you don't want to do that, find the ftp address and password and delete all the files. My ftp client of choice is https://filezilla-project.org/ . I'd take a local copy first in case they want it back. The address might be ftp.[mysite.tld] depending on the hosting.
If you are really stuck talk to the hosting provider. You can get some info about the hosting from a whois lookup on the ip address: https://who.is/
Related
I will integrate a rest api for my website. Integrator company wants an IP address for restrictions. I will send my computer ip for development and website (provider: heroku) ip for production. But i cant figure how the obtain these informations. Can anybody help or send an documentation about it?
Heroku does not provide a static IP.
Yet, here are 3 ways to make it work :
Give the domain address instead of an IP address to the integrator.
As Heroku is using volatile IP addresses, This is the best way.
Use an Add-on, Fixie or Guru301 seems to do exactly that
not recommended : Add a DNS A-record You can hard code your IP but it doesn't look stable
I have setup filezilla server on my computer, and i would like to access it via ftp over the internet.
I have a domain name in place already (example: myftpsite.com) i would like this to point to the ftp server, but i do not have a static ip. I know that static ips are much better since you dont have to worry about changing the dynamic every few weeks or months. But i still dont want to use them.
I do not want to use dyndns or any other dns software. I know this can be done without it i just cant figure out how.
Thanks,
Zac
The alternative to dyndns is you can update your DNS records every time your IP changes manually, or make your own program/script that does so.
dyndns is just a program that does this automatically. It updates your name servers every time your IP changes.
The manual alternative would be to type your IP address into your DNS provider whenever it changes.
There isn't another way to do it, thats just how DNS works.
Newbie programmer here. I'm building an app for an API that requires an IP address for authentication. Basically, users have to send the API management their IPs and then each time a computer makes a request to their server, it verifies whether it's coming from a registered IP.
Since I work in a number of different places and thus end up with different IPs, I thought it would be easiest to use DynDNS to establish a URL that points to whatever my current IP is and then send that URL to the API management. So my first question is if this approach would in fact work?
Secondly, assuming this would work, I set up ben.dynalias.com and downloaded the DynDNS Updater client. It appears to be working: the updater says status: OK and displays my current IP. However, when I navigate to the URL (ben.dynalias.com) there's no response. Should this be the case? How can I tell if it's working?
I don't see any reason it shouldn't work as long as your updaters aren't overwriting each other by running at the same time automatically from different locations.
You can ping ben.dynalias.com and see if your current ip matches.
I just hosted ben.dynalias.com and it gave me your IP.
Since there is no web server running on that IP, then your browser will not be able to show you a page result.
You can use http://www.kloth.net/services/nslookup.php
to check and see if you get the correct IP from a host lookup.
Depending on how often your IP changes this might not be a great solution as the DNS will cache your hostname and will not try and resolve it again until the TTL expires normally minimum 1 hour.
whether the API management accepts a hostname instead of an IP address is a question only they can answer. Some will, many won't as it's "easier" to hijack a domain name than to hijack an ip address.
trying to browse to you-address.dynalias.com that points to your own public address rarely works, even if you opened up the right ports because your router will be highly confused. The best way to test such a setup is by using a phone or tablet with 3g/GPRS internet - of course after you set up port forwarding in the router to point the appropriate port to your computer.
I need some help, I can not find my answers, certainly because I am not asking my self the right questions. So here's the thing, in my very own home, in the very own room I'm writing this I got a dedicated machine running apache server. As well I bought the cheapest domain name I could find in order to make some experiments. But I can not seem to point my domain to my dedicated server. I don't understand how to do it. I suppose it important to say that my ISP uses dynamic IP addresses. Could someone point me toward some documentation please?
When you are talking about your very own home, than you are talking about sitting behind a NAT. Thats means, that your router/gateway has to forward Port 80 to your apache server.
Moreover, you have to use a dynamic DNS solution (dyn.org, no-ip.com, ...) to link a domain to your dynamic ip address.
However, it is not possible to link a generic domain to a dynamic ip address.
I am thinking of methods to restrict public users from accessing sites on our staging server. The best method I can think of at the moment is use:
Deny from all
Allow IP Addresses
If I add this to vhost configuration then it will do what I need.
Is there any better ways of doing this? If I added our work based IP address to each vhost configuration and then the IP address was changed for any reason it would be pretty annoying to modify each one.
Also, some of the sites have test order information on, is this a secure method for doing this?
Thanks in advance,
Ian
Since an IP address can be spoofed this is not 100% secure. You may want to look at adding basic authentication where you can manage users and passwords rather than ip address (you may be able to leverage an exisiting identity system to make this easier (e.g. LDAP etc.).
Looking beyond that you may want to look at chef or puppet to automate the management of your users.