Jump to content

Recommended Posts

Posted

Hi Guys, sorry to hear you are having a tough time. I was on ricky and my

domain was parked there. The change was done very recently, on the 20th may.

 

It went from:

ns.rcp.net.pe

ns2.rcp.net.pe

 

To your

Ns1.heliohost.org

Ns2.heliohost.org

 

How can o regain control over the dns settings?

 

Thanks

 

Sorry, foegot to add that my username is martinf and my email is

martin@fulgueiras.pe

 

Thanks

 

El 27 jun. 2017 16:31, "Heliohost Support" escribio:

 

> Your message (Dns problems) has been assigned the tracking ID [HH#31878].

> One of our volunteer community members will reply to your email as soon as

> possible.

>

> Please include the string [HH#31878] in the subject of any future email

> regarding this case. You may do that by simply replying to this message.

>

> Please be aware that our system rejects binary attachements. If you are

> submitting a screenshot or attachement please post a link to the file

> instead of attaching it to the email.

>

> You may view the status of your ticket by visiting:

>

> http://www.helionet.org/index/index.php?showtopic=28618

>

> Thank you,

> Heliohost Support

> http://www.heliohost.org/

> http://www.helionet.org/

>

> -----Original Message-----

>

> Return-Path:

> Delivered-To: support@heliohost.org

> Received: from tommy.heliohost.org

> by tommy.heliohost.org (Dovecot) with LMTP id

> haceAK/OUlldEgAAY4nxBQ

> for ; Tue, 27 Jun 2017 14:31:27 -0700

> Return-path:

> Envelope-to: support@heliohost.org

> Delivery-date: Tue, 27 Jun 2017 14:31:27 -0700

> Received: from mail-pg0-f42.google.com ([74.125.83.42]:33202)

> by tommy.heliohost.org with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-

> SHA256:128)

> (Exim 4.89)

> (envelope-from )

> id 1dPy4w-0000Wg-KR

> for support@heliohost.org; Tue, 27 Jun 2017 14:31:26 -0700

> Received: by mail-pg0-f42.google.com with SMTP id f127so21543903pgc.0

> for ; Tue, 27 Jun 2017 14:31:02 -0700 (PDT)

> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;

> d=tinkay.com; s=google;

> h=mime-version:in-reply-to:references:from:date:message-

> id:subject:to;

> bh=mt6BUcCj72UzZukeZkB2wJSlZSjMPbpd/DbOs65BtWA=;

> b=mPpeT193wUkOoECDLfH5jfaZGkZPaJM1un1O2Nc9UyZ4VCzAsrSGGyLpo/

> XFZEAGRZ

> VmHVzYm2l3X6DAXE55p3lXMloACaM3JNQ4WIUysNFi+

> rRjzdLqbY3dQbE4pX1gCRyLkc

> ASFHFAU/UqqdZUmWMyTgowfkARzptjwtq1Ii0=

> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;

> d=1e100.net; s=20161025;

> h=x-gm-message-state:mime-version:in-reply-to:references:from:date

> :message-id:subject:to;

> bh=mt6BUcCj72UzZukeZkB2wJSlZSjMPbpd/DbOs65BtWA=;

> b=EEc/SCGTnpaJE5RBX/e5hlzeEiLMqB37KmZr+

> j31CDOcrwzpKx82O3vt8AFycpaZIK

> 4EsZX9rPVN5SH7FphhE18SbY86ca2L+D/ys+DueCzBwfBc/

> 5FahPE7DGRfi6oapBH1N+

> vNcIan/wsthwnOfZlffwD776GzBxKpIg5EBCc

> G0TIJjWgzxIhESiMHnqbL027x7loIUF

> j2dCRhzq/+tJ798jgl6Xvg6rUUwn/tMWVs3ASq0pak08soR7Gne+

> nUoGbQV8frVPv0s0

> JcWsf9ivoXP5nxmYNydrE+uCcnpSB12mpH/mc54hTAIt8ZIVhWXTN0zYfR4qd9gPu

> SFy

> lp4Q==

> X-Gm-Message-State: AKS2vOxTDzG6QwgpiT3OH6zfm8A0nK

> Nx4NCT742pN9isCisXwilKjWRH

> nXBtChF44eZ/Ro3l2MMp39JFM+MtAkN5

> X-Received: by 10.84.143.131 with SMTP id 3mr7828298plz.291.1498599041710;

> Tue, 27 Jun 2017 14:30:41 -0700 (PDT)

> MIME-Version: 1.0

> Received: by 10.100.189.67 with HTTP; Tue, 27 Jun 2017 14:30:40 -0700 (PDT)

> X-Originating-IP: [201.240.21.196]

> Received: by 10.100.189.67 with HTTP; Tue, 27 Jun 2017 14:30:40 -0700 (PDT)

> In-Reply-To: gmail.com>

> References: mail.gmail.com>

>

>

>

>

> From: Martin Fulgueiras

> Date: Tue, 27 Jun 2017 16:30:40 -0500

> Message-ID: gmail.com>

> Subject: Dns problems

> To: support@heliohost.org

> Content-Type: multipart/alternative; boundary="

> 94eb2c11ac3a8ad27a0552f7c79b"

> X-Spam-Status: No, score=-0.3

> X-Spam-Score: -2

> X-Spam-Bar: /

> X-Ham-Report: Spam detection software, running on the system "

> tommy.heliohost.org",

> has NOT identified this incoming email as spam. The original

> message has been attached to this so you can view it or label

> similar future email. If you have any questions, see

> root\@localhost for details.

>

> Content preview: Hi Guys, sorry to hear you are having a tough time. I

> was

> on ricky and my domain was parked there. The change was done very

> recently,

> on the 20th may. It went from: ns.rcp.net.pe ns2.rcp.net.pe To your

> Ns1.heliohost.org

> Ns2.heliohost.org [...]

>

> Content analysis details: (-0.3 points, 5.0 required)

>

> pts rule name description

> ---- ---------------------- ------------------------------

> --------------------

> -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,

> no

> trust

> [74.125.83.42 listed in list.dnswl.org]

> -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3)

> [74.125.83.42 listed in wl.mailspike.net]

> 1.5 SPF_SOFTFAIL SPF: sender does not match SPF record

> (softfail)

> -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%

> [score: 0.0008]

> 0.0 HTML_MESSAGE BODY: HTML included in message

> 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not

> necessarily valid

> 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid

> -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders

> X-Spam-Flag: NO

>

> --94eb2c11ac3a8ad27a0552f7c79b

> Content-Type: text/plain; charset="UTF-8"

>

> Hi Guys, sorry to hear you are having a tough time. I was on ricky and my

> domain was parked there. The change was done very recently, on the 20th

> may.

>

> It went from:

> ns.rcp.net.pe

> ns2.rcp.net.pe

>

> To your

> Ns1.heliohost.org

> Ns2.heliohost.org

>

> How can o regain control over the dns settings?

>

> Thanks

>

> --94eb2c11ac3a8ad27a0552f7c79b

> Content-Type: text/html; charset="UTF-8"

> Content-Transfer-Encoding: quoted-printable

>

> Hi Guys, sorry to hear you are having a tough time. I

> was=

> on ricky and my domain was parked there. The change was done very

> recently=

> , on the 20th may.

It went

> fro=

> m:ns.rcp.net.pe

> >=C2=A0 hr=

> ef=3D"http://ns2.rcp.net.pe">ns2.rcp.net.pe

dir=3D=

> "auto">

dir=3D"=

> auto">To

> your=C2=A0 dir=3D"auto">Ns1.heliohost.org st=

> yle=3D"font-family:sans-serif">Ns2.hel=

> iohost.org style=3D"font-family:san=

> s-serif">

How

> c=

> an o regain control over the dns settings? dir=3D"auto"> ont face=3D"sans-serif">

face=3D"sa=

> ns-serif">Thanks

 

>

> --94eb2c11ac3a8ad27a0552f7c79b--

>

>

Posted

While you're waiting for the manual backup (it may be a week or so), in the meantime, you're welcome to create a new account on Tommy or Johnny and add that domain as a parked domain to the new account so that it has something showing until we get you the backup.

 

If you decide to do this and it fails, please let us know and we can clear out the DNS entries so it will add to your new account.

Posted

Thanks, the thing is i only use the domain as email. I don't have a website

yet.

 

Me and 3 users are not receiving email since the 22nd. By creating a new

account can I create new mx records to point to google?

 

Thanks for the help

 

2017-06-27 17:04 GMT-05:00 Heliohost Support :

 

> While you're waiting for the manual backup (it may be a week or so), in

> the meantime, you're welcome to create a new account on Tommy or Johnny and

> add that domain as a parked domain to the new account so that it has

> something showing until we get you the backup.

>

> If you decide to do this and it fails, please let us know and we can clear

> out the DNS entries so it will add to your new account.

>

>

> You may view the status of your ticket by visiting:

>

> http://www.helionet.org/index/index.php?showtopic(618

>

> Thank you,

> Heliohost support

> http://www.heliohost.org/

> http://www.helionet.org/

>

>

 

--

W: www.tinkay.com

FB: www.facebook.com/tutinkay

Posted

When we cleaned up Ricky's crash, we removed all of the DNS records for all of the domains that were hosted on Ricky, which is why it no longer works.

 

You can just create a new account (I'd recommend Tommy, his registrations open at midnight UTC and fill quickly), add the domain to your new account, then go to the MX records section of cPanel and change them to Google. That will recreate the DNS records for your domain and make your email work again.

Posted

Perfect! thanks for the help

 

2017-06-27 17:22 GMT-05:00 Heliohost Support :

 

> When we cleaned up Ricky's crash, we removed all of the DNS records for

> all of the domains that were hosted on Ricky, which is why it no longer

> works.

>

> You can just create a new account (I'd recommend Tommy, his registrations

> open at midnight UTC and fill quickly), add the domain to your new account,

> then go to the MX records section of cPanel and change them to Google. That

> will recreate the DNS records for your domain and make your email work

> again.

>

>

> You may view the status of your ticket by visiting:

>

> http://www.helionet.org/index/index.php?showtopic(618

>

> Thank you,

> Heliohost support

> http://www.heliohost.org/

> http://www.helionet.org/

>

>

 

--

W: www.tinkay.com

FB: www.facebook.com/tutinkay

Guest
This topic is now closed to further replies.
×
×
  • Create New...