Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
These are examples, I have never used them, know nothing about them.
Google for "buy domainname" in your own language.
These require DNS for our webhost and since my machine is the host, so I want to configure DNS for my machine.
Therefore, first I have to configure DNS and require those steps.
I'm not sure I understand you.
For DNS, you need a valid domainname. Then you set the nameservers to be used, normally done in registrars web interface.
You can use registrars nemeservers if you want, and point 'www.' and whatever url you like to your public ip.
Example, my domain 'tuxit'se':
Code:
Extract from "#whoios tuxit.se"
nserver: ns3.binero.se
dnssec: unsigned delegation
status: ok
registrar: Loopia AB
So I have bought the domainname from Loopia AB, then in Loopias controlpanel (webgui) I changed nameservers to ns#.binero.se
Then, in Bineros controlpanel I have my DNS records.
Code:
* A 3600 195.74.38.17
@ A 3600 195.74.38.17
ftp A 3600 195.74.38.22
www A 3600 195.74.38.17
So, my website is on host with public ip 195.74.38.17
Last edited by pingu; 09-02-2012 at 03:34 AM.
Reason: Spelling
Nope - not if want it to be publicly available.
Using a domainname of your own means you have to set up your own dns-servers. Noone else will use them no matter how publicly available they are.
(Also, trying to set up a personal, publicly available nameserver will give you LOTS of headache! The only people I know of that do that are criminals who try to lure people to their sites.)
But domainnames aren't that costly, I pay around 10 euro / 15$ per year for a domainname.
Nope - not if want it to be publicly available.
Using a domainname of your own means you have to set up your own dns-servers. Noone else will use them no matter how publicly available they are.
(Also, trying to set up a personal, publicly available nameserver will give you LOTS of headache! The only people I know of that do that are criminals who try to lure people to their sites.)
But domainnames aren't that costly, I pay around 10 euro / 15$ per year for a domainname.
I have configured DNS server for private IP on my machine and I want to see if I can set it for public IP. I am doing this to gain knowledge, not for any business or any criminal activity.
If you have your own dns server then you can use it to point any url you like to your public ip.
But only you will use it - well, of course you could ask some friends to use your dns server as their third.
You could put up a dns server accessible from outside, but as I said earlier noone will use it.
I don't know if you can get into trouble doing this. Probably not if your personal domainnames are clearly yours and do not exist in real Internet - but I don't know!
Alos legislation differs between countries.
Private dns servers are commonly used on private networks only, not publicly available.
The reason for that, and the legal problem you might run into, is because one way to steal money is to fiddle with dns & nameserver settings.
So, if you want your site available publicly: buy a domainname.
If you just want to play around & learn, set up a private network. In there you can use whatevere domainnames you like. (But beware, if you choose domainnames also used IRL, you will not be able to reach those sites.)
If you have your own dns server then you can use it to point any url you like to your public ip.
But only you will use it - well, of course you could ask some friends to use your dns server as their third.
You could put up a dns server accessible from outside, but as I said earlier noone will use it.
I don't know if you can get into trouble doing this. Probably not if your personal domainnames are clearly yours and do not exist in real Internet - but I don't know!
Alos legislation differs between countries.
Private dns servers are commonly used on private networks only, not publicly available.
The reason for that, and the legal problem you might run into, is because one way to steal money is to fiddle with dns & nameserver settings.
So, if you want your site available publicly: buy a domainname.
If you just want to play around & learn, set up a private network. In there you can use whatevere domainnames you like. (But beware, if you choose domainnames also used IRL, you will not be able to reach those sites.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.