What happen to my DNS Zone if Linode Crash?

Hi everyone and thanks for this great forum!

I set up on my small Linode 2 DNS Domain Zone, 2 Reverse DNS, 2 DKIM records for Google Apps for Business and i'm very happy!

I have only a stupid question: if my Linode crash my 2 DNS Zone also could crash and i do NOT receive emails?

I know that my 2 Domain Zone are linked to my Linode. In others words: DNS Zone have or NOT an independent life?

Really thanks!

5 Replies

If you are paying for at least one Linode, the domains in the Linode DNS Manager will continue working, even if your Linode is broken or unreachable. (That's the major reason for using the DNS Manager instead of running your own DNS servers.)

Your reply is gold for us and i have 2 more questions :)!

> That's the major reason for using the DNS Manager instead of running your own DNS servers.

If the DNS Manager works in indipendent way why i need to link my paid Linode?

Why the best is always use Linode DNS Manager and not Domains Registrar DNS Panel (often very basic)?

Sorry but before i do not use my own DNS servers but Registrar DNS Panel linked to Linode with Record A !

> If you are paying for at least one Linode
Sure i have 2 DNS Zone linked to my small 1 Linode (Linode 1GB - basic plan) .

> You should always set the reverse DNS, even if your Linode hosts more than one domain name.
Please confirm that this is really correct? I see that more people have some problems with this :)

@under:

If the DNS Manager works in indipendent way why i need to link my paid Linode?

Why the best is always use Linode DNS Manager and not Domains Registrar DNS Panel (often very basic)?

Sorry but before i do not use my own DNS servers but Registrar DNS Panel linked to Linode with Record A !
It's okay to use your registrar's DNS instead of Linode's, as long as you set up the correct A record. You may prefer Linode's DNS if you need more advanced features, but most registrars nowadays are perfectly fine for a typical website.

@under:

> You should always set the reverse DNS, even if your Linode hosts more than one domain name.
Please confirm that this is really correct? I see that more people have some problems with this :)
Every Linode already has reverse DNS set up correctly. You shouldn't have any issues if you just keep the default hostname and reverse DNS. It may be a good idea to use some subdomain of your own domain as the reverse DNS entry if you're running a high-volume mail server, but most people don't need to. It's been a few years since I've touched the reverse DNS entry for any of my Linodes, and I've never had a problem with the defaults.

Really thanks for another gold reply!

So, if the DNS Manager works as indipendent why i need to link it to my Linode?

> Every Linode already has reverse DNS set up correctly. You shouldn't have any issues if you just keep the default hostname and reverse DNS. It may be a good idea to use some subdomain of your own domain as the reverse DNS entry if you're running a high-volume mail server

Linode Documentation: > You should always set the reverse DNS, even if your Linode hosts more than one domain name.

The question is: if i have 3 domains name on only 1 small Linode the best is to have 3 IP for best results with Reverse DNS?

Sorry this is very important for all!

Really thanks!

Linode Documentation: > You should always set the reverse DNS, even if your Linode hosts more than one domain name.

The question is: if i have 3 domains name on only 1 small Linode the best is to have 3 IP for best results with Reverse DNS?

Sorry this is very important for all!

Really thanks!

That's not necessary. The PTR for your Linode's IP should point to the FQDN of the Linode. There's no need to have 3 IPs for three domains.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct