Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate DNS and NS management to Engineering, esp. Snowplow, including process docs for maintaining #59

Open
MeltyBot opened this issue Mar 1, 2022 · 10 comments

Comments

@MeltyBot
Copy link

MeltyBot commented Mar 1, 2022

Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/65

Originally created by @afolson on 2022-03-01 00:37:57


I've moved DNS hosting from SiteGround to Route 53 and need to update the handbook. This should also include documenting the sp NS records per https://gitlab.com/meltano/marketing/website/-/issues/11#note_855914523

@afolson afolson removed their assignment Jul 5, 2022
@therebbie
Copy link
Contributor

@afolson I see that Route 53 is documented in the handbook. I'm not sure what you mean above re: the sp NS records. There is no reference in the linked issue to that. There is a reference to here that says to make sure to document the differences for sp and why -- though there is no detail given. I will note that the NS records for sp are different, though:

sp.meltano.com. 21600 IN NS ns-1020.awsdns-63.net.
sp.meltano.com. 21600 IN NS ns-1191.awsdns-20.org.
sp.meltano.com. 21600 IN NS ns-2013.awsdns-59.co.uk.
sp.meltano.com. 21600 IN NS ns-355.awsdns-44.com.

and

meltano.com. 21600 IN NS ns-1488.awsdns-58.org.
meltano.com. 21600 IN NS ns-1953.awsdns-52.co.uk.
meltano.com. 21600 IN NS ns-309.awsdns-38.com.
meltano.com. 21600 IN NS ns-709.awsdns-24.net.

@aaronsteers aaronsteers changed the title Add information about updating DNS, document sp NS records Migrate DNS and NS management to Engineering, esp. Snowplow, including process docs for maintaining Jan 17, 2023
@aaronsteers
Copy link
Contributor

aaronsteers commented Jan 17, 2023

@magreenbaum - I'm assigning this to you but you can also delegate to another team member if someone else is able to pick up. This is one area where @afolson jumped in to help us get this set up, but we really should be owning in Engineering long-term. This was originally created solely as a 'process docs' issue in the Handbook repo, but feel free to open an infra-side issue as well if consolidation is helpful in long-term management.

@magreenbaum
Copy link
Contributor

magreenbaum commented Jan 18, 2023

@aaronsteers @afolson No problem moving this to engineering. I do have a few questions about it.

  • I see that the NS records for sp.meltano.com are located in our meltano org AWS account in the meltano.com hosted zone but which account is the sp.meltano.com zone hosted? I checked snowplow but it's not in there. My concern is if it's located in snowplough, the suspended account.
  • What is this subdomain used for?

@afolson
Copy link
Contributor

afolson commented Jan 18, 2023

@tayloramurphy @pnadolny13 You all set Snowplow up right? sp.* was just delegated to snowplow to manage DNS or something right? How is that managed?

@aaronsteers
Copy link
Contributor

Cc @WillDaSilva, @pnadolny13 in case they have additional context.

@tayloramurphy
Copy link
Contributor

@magreenbaum I've invited you to the snowcatcloud channel in slack which has more info on the snowplow domain

@magreenbaum
Copy link
Contributor

magreenbaum commented Jan 18, 2023

Thanks @tayloramurphy for adding me to that channel. So we're just setting our NS records for sp.meltano.com to allow snowcatcloud to host the DNS record is my understanding.

@therebbie
Copy link
Contributor

@magreenbaum As part of this effort I'd like to make sure we at least consider all of our domains. The complete list is here. Ideally we would have all of these with a single registrar (not, alas, possible), and a single DNS provider.

@magreenbaum
Copy link
Contributor

@therebbie sounds good. I'll update the docs for this issue as needed and then move the rest to an internal issue (around migrating to a single DNS provider).

@magreenbaum magreenbaum removed their assignment Oct 31, 2023
@magreenbaum
Copy link
Contributor

Heads up @cjohnhanson, I've removed my assignment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants