[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.
Related
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..
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
My client has a website at exampleA.com, but want their new domain name exampleB.com to point to the server that hosts exampleA.com.
They have certain emails setup with exampleB.com...so I want to avoid changing the name servers, in case I mess with these settings (I don't know all the info yet).
If I simply want exampleB.com to point to a different server, what DNS records should I change? I have a static IP for the server.
Is it just the A record I need to modify? I'm not good with this DNS malarkey.
Thanks for your help.
Mikey.
Yes, just update the A record. You may have to update the web server config file on exampleA.com server to listen and serve the requests for exampleB.com.
If the static IP address you have is in IPv6 format then you would have to update the AAAA DNS record.
Yes, by changing A record in the domain account will solve the problem. In this case, you do not need to change the nameserver in the domain account
everyday i get following email from the cpanel, i dont know what it means and in current configuration, i have a one ip for a ns1.nameserver and one for ns2.nameserver but top level domain nameserver is mapped to one ip address. but there is no way to add a another A record to there (i dont knw how) or i want to disable this notice out, since still all works fine in the network...
The hostname (nameserver.com) resolves to 67.xxx. It should
resolve to 67.xxxx. Please be sure that the contents of
/etc/hosts are configured correctly, and also that there is a
correct 'A' entry for the domain in the zone file.
Some or all of these problems can be caused by /etc/resolv.conf
being setup incorrectly. Please check that file if you believe
everything else is correct.
You may be able to automatically correct this problem by using the
'Add an A entry for your hostname' option under 'Dns Functions' in
your Web Host Manager.
Two ways to resolve the issue.
Add the correct A record for the IP and Fully Qualified Domain name
Per cPanel it is not suppose to function behind a NAT though as many have found this does in fact work. So you can "Fix" or stop this message by going into the contact manager and disable the “Ip address dns check” option
You need to make sure that you have properly added A record for your hostname and assigned it to IP address of your server. For example, if your server hostname is xyz.abcd.com then you need to add xyz A record in abcd.com DNS zone and point it to your server IP address.
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.