Home » LxCenter » Contributed HOWTOs » DNS setup(What is all this fuzz about DNS templates?)
| DNS setup [message #84642] |
Fri, 03 June 2011 19:26  |
|
Hi,
today I get to teach a whole lesson all By myself. And I'm gonna teach something relevant something modern. The internet. The internet is really really great ....
DNS:
DNS servers are also called nameservers. Their role is to translate human readabel internet addressess (URLs, like www.lxcenter.org) into computer understandable numbers (IP addressess). This is called resolving.
Records:
Some, not all.
A record: this is the record that assigns a name to an IP.
MX record: this record holds the hostname(!) of the server, that is handling the mail of the given domain. Hostname, but not the IP! This means you'll have to set up an A record to that host.
NS record: this record tells the world the hostname(!) of your DNS servers. This means you'll have to set up an A record for all of them.
So the key is, where you dont write IP, but only hostname, you MUST set up an A record for that host (if it does not have it through an other nameserver).
Kloxo DNS template:
You create a template for all domains that share the same namesevers. So this way you wont have to set up all of them separately.
Registrar's nameserver or mine?
The basic idea behind DNS what many newbies dont understand is that, one MUST have authority over a domain or the world wont ask him about it's dns records. I'll try to rephrase it: if the world is not told by _your_ _registrar_ about your nameservers, then people wont get the informaiton about your domain from your nameservers!
For that either you mail your registrar to have your domian's NS point to you, or you change the corresponding NS record through some webpanels.
THIS IS INEVITABLE! Without this your domain wont be resolved in the way you set it through kloxo.
If you have a client who does not want to use your nameservers, than you have nothing to worry about, you only have to setup his/her domain. You can use your default template, or ANY template as the world will receive information about the given domain through his/her registrar.
Interesting parameters of DNS templates:
There is a tab when you manage your DNS or setup new dns template, the General Settings.
Here you can choose SOA (Start of Authority Record) nameserver for your domain. The SOA defines global parameters for the zone (domain). Always choose one.
An other basic paramter is the TTL (Time To Live). By this parameter you can tell the caching nameservers of the world that how long should they keep the cached IP address of the domain. I believe it is handy to set it to a lower value ( like to 1 hour = 3600secs). Once you're done with setting up, dont forget to change it back.
OK, it's enough for now.
Please ask for details or more info if you need/want.
And once more: IF YOU DONT HAVE THE NS RECORD OF YOUR DOMAIN POINTED TOWARDS YOUR NAMESERVER (vps, kloxo server, call it as you want) AND DONT HAVE NS RECORDS AND THE CORRESPONDING A RECORDS SET UP FOR YOUR NAMESERVERS your domain will never resolv.
Best wishes,
Semir
P.S.: Who got the joke of my progolue? 
ProfiVPS.com Cheap VPS hosting! Buy it from me 
ProfiVPS.hu Megbízható, Olcsó VPS bérlés, Virtuális szerver bérlés
If I helped you, please consider putting my link on your site/blog! Thank you in advance
[Updated on: Mon, 20 June 2011 02:07] Report message to a moderator |
|
|
| Re: DNS setup [message #84661 is a reply to message #84642] |
Sat, 04 June 2011 05:21  |
|
Troubleshooting:
Checklist:
1. NS redirected at registrar
2. "A" records are set up on the dns server
3. NS records are given and good.
4. If you use your kloxo's nameservers create the template
a. The A records of your NS records should point to your server.
5. Domain authority is set
6. Lower the TTL
7. Check your firewall.
Use testers like intoDNS.com, or the host/nslookup command.
Test your server:
You can check your DNS setup any times using nslookup or the host command. (I prefer host, if you dont have it, do install it.) Run this command in a shell, replace with the correct values:
host -a yourdomain.com your_dns_server_ip
This will tell you if your dns server resolves the given domain or not.
Registrar wants two nameservers
The standards dictate two nameservers to be used if one wants authority over a domian. Tougher registrars will even want you to have them in separate locations, with IPs from other ranges.
If your regsitrar wants that, you have no other ways, but to set up a secondary nameserver somewhere far.
Open port 53 on the firewall!
Maybe this is not the best method for CentOS, but it's a good start.
http://wiki.lxcenter.org/How+to+secure+your+Kloxo+with+IPTAB LES
Do NOT make the script as an init.d script. Simply run it once, then run:
/etc/init.d/iptables save
This will create the centos firewall configuration files.
To be continued...
ProfiVPS.com Cheap VPS hosting! Buy it from me
ProfiVPS.hu Megbízható, Olcsó VPS bérlés, Virtuális szerver bérlés
If I helped you, please consider putting my link on your site/blog! Thank you in advance
[Updated on: Wed, 15 June 2011 04:21] Report message to a moderator |
|
| | |
| Re: DNS setup [message #85510 is a reply to message #85509] |
Mon, 20 June 2011 02:18 |
|
I asked my VPS provider for PTR.
but he said :
We only setup rdns. Let us know in this format how you'd like it setup.
123.123.123.123 server.mydomain.com
sorry for dummy question
|
|
| |
| Re: DNS setup [message #85702 is a reply to message #85511] |
Thu, 23 June 2011 09:38 |
|
semir wrote on Sun, 19 June 2011 23:24Reverse dns: when your domain is resolved into an IP.
This is all good, answer them the IP and domain you want to be resolved.
IP:server.mydomain.com = MyServerHostName.MyDomain(NameServerRegistered).Com
or
IP:HostName
which one ?
|
|
|
| Re: DNS setup [message #104920 is a reply to message #85702] |
Fri, 28 December 2012 00:20 |
|
felz wrote on Thu, 23 June 2011 06:38semir wrote on Sun, 19 June 2011 23:24Reverse dns: when your domain is resolved into an IP.
This is all good, answer them the IP and domain you want to be resolved.
IP:server.mydomain.com = MyServerHostName.MyDomain(NameServerRegistered).Com
or
IP:HostName
which one ?
The idea behind reverse DNS (rDNS) is to associate your IP address to the full mail server name, usually something like mail.mydomain.com. The reason you want to do that is that a lot of mail from your server will be rejected if the sending server name doesn't match your rDNS. The only way to do that is to have your VPS host create the rDNS association for you.
So, if your mail server operates as mail.mydomain.com then you would ask your VPS host to associate your IP address with mail.mydomain.com. The important thing the receiving server will look for is that the top level domain (mydomain.com in the example) matches the sending server name. It's not that interested in the "mail." prefix, but you should still give them your full mail server name.
Entomy Networks, Linux Shared & Reseller Hosting Services
Data Centers in USA (Chicago, IL) and Europe (Zlin, CZ)
|
|
|
| Re: DNS setup [message #105478 is a reply to message #104920] |
Mon, 04 February 2013 03:20 |
 ArcAiN6 
Messages: 113
Registered: July 2008 |
Valuable Member |
|
|
for those of you testing out at home, or hosting very very small kloxo servers from home, or dynamic IP address, you can skip most of this and use a service such as dnsexit.com to manage your DNS for you for free.
DNSexit is a free, dynamic DNS service, there are other out there, but DNSexit was the first one i came across with decent enough DNS management capabilities for it's free users.
Just points your registrar to use the DNS exit NS servers for your domain(s) and set up your DNS settings in dnsexit.
install the dnsexit client for updating your DNS via IP fetch, and you're good to go.
This is confirmed working from my test server here at home.
There is a drawback to this approach, you will NOT have reverseDNS capabilities due to the fact your ISP probably won't reverse for you.
[Updated on: Mon, 04 February 2013 03:22] Report message to a moderator |
|
|
| Re: DNS setup [message #105549 is a reply to message #105478] |
Fri, 08 February 2013 01:07 |
|
ArcAiN6 wrote on Mon, 04 February 2013 00:20for those of you testing out at home, or hosting very very small kloxo servers from home, or dynamic IP address, you can skip most of this and use a service such as dnsexit.com to manage your DNS for you for free.
In the case of a residential connection, port 25 will almost certainly be blocked anyway. Even if you overcome your dynamic DNS and rDNS problems, which is not going to be easy, you still have to face the blocked port 25 issue. You aren't going to be able run an MTA email server from behind a blocked port 25.
Outgoing email can be dealt with by configuring qmail to route outgoing email to the ISP's smtp server, or relaying through a 3rd party smtp provider who accepts traffic from a nonstandard smtp port.
Incoming email is another matter entirely. Email servers are not going to be able to communicate with qmail through blocked port 25, so you are left with no choice except to have a 3rd party provider accept your email and provide POP3 or IMAP services to you.
Really, the blocked port 25 issue is the most compelling reason to operate a server in a data center, even more compelling than the dynamic DNS and reverse DNS issues. Unmanaged VPS servers are inexpensive enough to make leasing a VPS practical for most any budget.
Entomy Networks, Linux Shared & Reseller Hosting Services
Data Centers in USA (Chicago, IL) and Europe (Zlin, CZ)
[Updated on: Fri, 08 February 2013 01:09] Report message to a moderator |
|
|
Goto Forum:
Current Time: Fri May 24 22:59:51 EDT 2013
Total time taken to generate the page: 0.01240 seconds
|
HyperVM & Kloxo Support
Members
Search
Help
Register
Login
Home
