This might be a stupid question but i would really appreciate any compact answer.
I have uploaded a Joomla site on my local machine using a static IP address (213.221.211.111 for example). I have registered a domain (like www.example.com) on Godaddy.com. Within their dashboard, I set the primary and secondary name servers (I looked it from my router setup page).
Is there any else I need to do so that entering e.g. www.example.com would take the user to 213.221.211.111.
Inside of godaddy, you need to map "www" to your static IP address. It would be a good idea to also map the default entry for your domain, sometimes called "#".
Edit: Upon further reading of your original question, you don't set the primary and secondary DNS servers for your domain to your ISP's servers. Your domain's primary and secondary servers are for the addresses of the servers that are responsible for serving your domain. Unless you have your domain hosted with your ISP and not with godaddy, then this is not the right thing to do at all. If you have your domain hosted with godaddy, follow their instructions for setting up a domain and pointing "www" at an IP address.
In addition to what jricher said, you will also probably need to port forward.
Related
Lets say I have ordered domain name abc.com from GoDaddy.
I want to point the domain to my web site that I am hosting locally on my computer via IIS. Lets say that to hit this website currently, you would go to '123.123.123.123/mysite/'.
I am trying to setup the DNS Zone File to do this, but I cannot figure out how to get it to point to the "/mysite/" directory.
How can I properly set my GoDaddy DNS Zone file to point to '123.123.123.123/mysite/'?'
You have got your concepts a little mixed up there. What you are looking for is a HTTP Redirect. DNS is simply a way to map an IP Address to a domain name, it doesn't care what the traffic does once it gets to your site.
Think of DNS as a Postcode (Zipcode). It puts a letter in your letterbox. There is no way for it to know that Betty is on the second floor, because that's not what the Postcode does.
DNS will point a domain name example.com to an IP Address 123.123.123.123. You can have multiple domain names, www.example.com and mysite.example.com all pointing to the same IP Address, and the server can be configured to figure out what to do with each individual domain name.
So what you could potentially do is have the server detect that you are requesting mysite.example.com and have that redirected to www.example.com/mysite. This would be the standard way of achieving this.
The company i work for just begun hosting a new website and had to transfer the domain name from the ISP to a different hosting company.
Now the website is accessible from outside the network but not accessible from inside the network. The ISP is the same and we can't access the website using our ISP. It doesn't resolve the DNS Name at all.
If i try to ping the website, it says "host lookup failed", even nslookup is failing. When trying to access the website via the IPaddress, it refuses.
The problem is in the ISP but I don't know how to solve it and our ISP isn't being very helpful.
This often happens when someone is running authoritative and recursive DNS on the same servers. Which is why you should never do that :)
It also happens when your local domain (Active Directory?) is the same as the domain you use at your hoster. Never do that. For example: if your domain is example.com then don't use example.com as your local domain. If you do then both your hoster and your own servers believe they are authoritative for that domain. Once the zone data starts to diverge you have this kind of weird problems. Instead use a subdomain of your domain name for your office, like office.example.com so that example.com can remain authoritative at the hoster.
If you do have the same domain both locally and at the hoster then you have to manually make sure that the information in your local DNS server stays in sync with the hoster's DNS server. For example: if your hoster has record www.example.com A 192.0.2.1 then you have to have the same record in your local DNS server. When the hoster changes the record to e.g. www.example.com A 192.0.2.222 then you have to make the same change otherwise your local DNS server will keep telling you that www.example.com is at 192.0.2.1. The same happens when you change hoster as they will almost certainly use different IP addresses.
So if you can then don't use the domain name itself in your office but use a subdomain. If that is impossible then you will have to manually keep the hoster's and your own DNS zone data in sync. Because this always goes wrong and breaks in 'interesting' ways really try to use a subdomain though!
PS: and never ever use somebody else's domain name as your local domain. I have seen ICT companies use local domains like <localcityname>.com and then suddenly the whole company can't access the real domain anymore because the local servers think it's theirs.
My client have a dedicated server on liquedweb cloud service and we my web app is hosted on that server. We want our users to map their domain to our server. So they can enjoy our web app by using their domain name. What information I need to provide to my user so he can map domain and what information I need from them?
I don't know much(in fact anything) about domain mapping
thanks
It depends if the server has a dedicated IP address or is natted.
If the server has a dedicated IP address you can ask your clients to point their entire domain to you server by adding the following A records:
Host TTL Protocol Type IP Address
# 300 IN A 1.1.1.1
www 300 IN A 1.1.1.1
Not all domain hosts ask for TTL,if not dont worry about it.
If you want just their subdomain to point to your server (subdomain.website.com)
subdomain IN A 0.0.0.1
TTL is optional in some systems, in this case the default will be used.
Generally it is recommended that you use an IP for the Apex record and not a domain name. EG: example.com is the apex, www.example.com is the www subdomain.
A typical configuration would be below:
Host TTL Protocol Type Result
# 300 IN A 1.1.1.1
www 300 IN CNAME example.com
This is the same config as the top example but using CNAME example.com. It is the same as using A 1.1.1.1, it just means you only need to change one record.
If your server details are a hostname and not an IP address, most systems will not let you use the hostname for the apex so you will need to find out the IP address. (A simple method is to use the nslookup command or dig command).
TTL is how long in seconds a record last before it expires. If you are unsure what you are doing I recommend lowering this so you can correct mistakes more quickly.
Different methods for the different servers. For most of the servers, you have to change the nameservers of your domain.
This mostly needs when your domain registrar and hosting provider both are different.
First Login into your hosting account, navigate to the account details,
then copy the nameservers from there...which would be like :- dns1.hostingprovider.com
dns2.hostingprovider.com
After that, Go to control panel of your domain. Navigate to the nameservers
You will see the link:- dns1.domainregistrar.com
dns2.domainregistrar.com
Paste the above links at the place of below links.
They need the IP address (and possibly instructions on how to configure their DNS servers (which means a variety of different sets of instructions for different servers and control panels)).
You need the domain name.
i need to point from my hosting account to my local server
so i thought the best way is to do it using a subdomain
though the issue is that i cant figure which is the right way to do it
using same DNS as my domain / leaving it blank
using my internet isp dns maybe ?
what is the right way to point a subdomain to a static ip of my isp internet account at home ?
You don't need a subdomain, you need an A record (address). You could set up a subdomain, and then use an A record within that, so, if your domain is example.com:
Your domain is set up as example.com, your public web server A record might be www.example.com. You could then set up your home server A record as homeserver.example.com
A sub domain might be 'home.example.com`, and a server in the sub domain will have an A record of myserver.home.example.com.
In all these cases the IP address of your A record should be the IP address of the network side (external side) of your home internet router. If the address is static this will work, but if it's not you'll need to subscribe to a DNS service that supports Dynamic DNS, and that's a whole different story.
How you go about setting all this up is ISP-dependent.
Note that the external address of your network will not match the internal address of your server, so you'll need to set up port-mapping on the router to allow inbound traffic to reach your server.
..and lastly, do you really want to risk opening up your home network to the ravages of the public internet? Do this only if you really know what you're doing, and possibly not even then.
I have been attempting to set up magento on a shared hosting server that doesn't support innoDB, ergo its not been possible. The domain I want to use has also been registered with this rubbish hosting provider. (one[dot]com for anyones reference). So I thought I would be able to point this domain to a different hosting provider that DOES support it, but one[dot]com doesnt allow me to change nameservers for the domain. They just said this:
You can only setup IP address, CNAME and web forwarding in our DNS settings but not change of nameservers
Would there be any way to change any of these settings or the .htaccess file so that, for example
http://www.mydomain.com/folder/page.php?query=string
Would display a page from the other server
http://xxx.xxx.xxx:xx/folder/page.php?query=string
I've created loads of sits doing all sorts but never really needed to other with the domain administration side of things.
You don't need to change name servers to map a domain to a different server. If the "good" provider supports it (i.e. allows you to register a domain on the server that isn't hosted by the company), just switch the A and MX records to the new server's IP address.
You do need the cooperation of the "good" provider for this, though.
If they're letting you set up the IP address, then setting the IP address of www.mydomain.com to xxx.xxx.xxx.xx should do the trick. On the other server, you'll need its webserver to be set up to serve www.mydomain.com as a virtual domain - if you're using a hosting provider they should do this for you; if not it should be fairly easy to set up (consult the manual of whichever web server software you're using).