I was trying to delete ns1.something.com and ns2.somthing.com records from the DNS functions using cPanel.. however the records has been successfully erased.. but when I go back to Nameserver IPs under newtworking setup.. I still can see them there..
is there any specific file I can access on my vps so I can remove them?
In CPanel?
I think DNS related operation need sometime to go into effect.
Just wait and try logout your CPanel again.
Related
Is it somehow possible to edit /etc/hosts on Heroku , through the buildpack or otherwise?
I have a couple of dev sites that I need to connect to that don't have DNS entries, so I need to add a couple entries to /etc/hosts.
Thanks
I am pretty sure that's not possible. However, why can't you just specify the IP of whatever host you're trying to connect to, instead of specifying a host name? Also, if you absolutely must, I suppose you could create entries in a DNS server of a domain of your own (say: mydomain.com), and then specify myhost.mydomain.com.
I am trying to migrate the Joomla website from its temporary server to the new server using akeeba kikstart, during the migration everything looks ok but once the migration finishes then the website on the new server looks odd. This is the website which I am trying to migrate: http://46.20.125.254/~scfgroup/ and this is how its look like after the migration: http://www.scflegalandcorporateservices.com
does anybody know why is this happening? how could I solve this migration problem?
any help appreciated.
I never use any 3rd party tools for taking backups, transferring etc. I believe in doing it manually which out of all honest, is very simple.
Zip up the original site and upload it to the FTP of your new host, then extract.
Export the database from your original site and import it on the new host using PHPMyAdmin
Open the configuration.php and edit the database area so they they match the settings for your new server.
Hopefully should work after.
Nothing to worry, your joomla migration process went on well. If the website site is accessible through IP, but not the domain, then this is probably because
the ISP blocks the domain (unlikely)
the DNS server you use has some hiccups
Try changing the DNS server addresses specified in the internet connection to either
Google DNS: 8.8.8.8, 8.8.4.4 or
OpenDNS: 208.67.222.222, 208.67.220.220
There are a couple of other free DNS services, but those are the ones used by most, I guess. Otherwise address this issue with your hosting provider.
I have looked this up and what was described in other answers did not work for me. I created a elastic ip from my ec-2 dashboard, and I set the A records of my domain (www, *, and #(none)) but it does not work. When I try to go directly to the ip address it also does not work though so I am not sure why this is happening.
Also where exactly does the elastic ip point? To my home folder, to the ec-2 user? It is not working now so I couldn't test it, but when it does work I still won't know.
Two things: remember that your domain will need to propagate, so leave it a few hours. Also, your elastic IP points to the machine you bound it to.
Almost forgot, you also need to edit your security zone to open up ports to allow incoming connections on those ports, as the default is to block everything except SSH.
One of my sites - mediadeals.co.uk is showing a blank page.
So I went back to my developer. He asked me to add this on my hosts file
in windows->system32->drivers->etc->hosts
74.86.205.232 mediadeals.co.uk
After doing this the site started working. What does this mean?
Thats crazy. All he did was make it work on YOUR machine. The hosts file simply maps names to IP addresses. Its like a local DNS. What needs to happen for the outside world to see this the DNS servers that are authoritative for mediadeals.co.uk need to have an A record pointing to 74.86.205.232.
How long ago did you register that site name? Don't forget that DNS entries may take a while to propagate across the web. 24 hrs+ sometimes.
And btw, that "fix" will ONLY work on your machine. It maps the friendly URL to an IP address for you, not for the world.
The reason its not working is there is no DNS record for it.
The hosts file is allowing you to point via a local DNS replacement.
All you need is to get the site hosted somewhere and a DNS entry setup.
If you like the site and he is willing to host for $150 then go for it, depending on your contract, if he should have done in the initial budget then you should question this.
RE
I recently moved hosts with my blog and I have waited 72 hours for it t propergate properly. I just checked the site there and it's showing it on the old host. When i use a proxy, I can see the site perfectly on the new host. The problem seems to becoming from my PC.
EDIT: Tried to flush the dns and it's the same story, it's quite weird.
Any idea?
Your old DNS records will live in various DNS caches until their TTL (time-to-live) timers expire.
Best practice is to revise your DNS records well before the move, and pull the TTL (time-to-live) timeout values low, leaving enough time for the old records to timeout and get refreshed with the short-TTL records. Then after the move you put the TTL values up on the new records (for efficiency).
Now that you're in this situation, you'll have to put up with the inconsistency until all the cached records expire. If you have a way to put an HTTP redirect on the old web server, pointing to an IP URL, that could tide you over in the short run.
Your ISP is the one the one caching the record. Uses a hosts file http://en.wikipedia.org/wiki/Hosts_file to temporarily force your computer to use the new ip address.
Sounds like you have the DNS cached on your box. This could be cached on your PC or at your DNS server. Short term options; can try to flush your DNS cache, you can edit your hosts file to temporarily point at the right location.
Open a command prompt and type:
ipconfig /flushdns
then try your site again.
I see this:
www.keithdonegan.com [81.17.254.87]
My DNS changes always propagate in minutes, a couple of hours at the most.