Jump to content

helioma

Members
  • Posts

    3
  • Joined

  • Last visited

helioma's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi! Can you unarchive my account? Thank you
  2. I want domain.com and www.domain.com to continue to resolve through Google Domains, and of course the MX records have to be retained by Google in order to keep their 100% uptime options. How about these? 1. I expect to create an NS record for new.domain.com pointed to ns1.heliohost.org 2. Or I can CNAME from new.domain.com to the heliohost domain too Which of those options would best meet heliohost requirements?
  3. HI folks. I am trying to create an addon domain to my heliohost.org account. I own the primary "domain.com", and I'm trying to add "new.domain.com" # When creating the addon domain I receive the following error: "(XID qffka8) Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameserver." * My goal is to keep "domain.com" controlled by Google Domains (this protects emails), and to have "new.domain.com" pointed to the addon domain on heliohost. * I cannot do the NS redirection at "domain.com" since Google requires primary control of "domain.com" My plan was to create an ns record for "new.domain.com" >> "ns1.heliohost.org" Which would mean "nslookup new.domain.com ns1.heliohost.org" would resolve correctly. But... I cannot get past creating the addon domain. Any recommendations?
×
×
  • Create New...