From: Christopher Baines <mail@cbaines.net>
To: guix-sysadmin@gnu.org
Cc: 37320@debbugs.gnu.org
Subject: [bug#37320] [PATCH] hydra: dns: Add "data" to point at milano-guix-1.
Date: Fri, 06 Sep 2019 15:10:14 +0200 [thread overview]
Message-ID: <87a7bhbmfd.fsf@cbaines.net> (raw)
In-Reply-To: <20190906114441.19067-1-mail@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 2043 bytes --]
Now that milano-guix-1 is back online, I'm interested in sorting out
configuration for nginx, as well as letsencrypt for a TLS certificate.
For that, it's probably useful to think about the DNS configuration. I
think that this is something that has been discussed a bit in the past,
but at that time there were some improvements I wanted to make before
making anything more public.
But, over the last month I've fixed some of the problems I knew about
and added new features, so I'm happier at this point with it being more
widely available.
So, I've started looking at setting up the DNS configuration, and I've
sent this patch which I think is the relevant change in the maintenance
repository.
Thanks,
Chris
Christopher Baines <mail@cbaines.net> writes:
> * hydra/modules/sysadmin/dns.scm (milano-guix-1-ip4): New variable.
> (guix.gnu.org.zone): Add "data" to point at milano-guix-1, and update
> the serial.
> ---
> hydra/modules/sysadmin/dns.scm | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/hydra/modules/sysadmin/dns.scm b/hydra/modules/sysadmin/dns.scm
> index 164caf1..ef1f265 100644
> --- a/hydra/modules/sysadmin/dns.scm
> +++ b/hydra/modules/sysadmin/dns.scm
> @@ -47,6 +47,7 @@
> (define hydra-ip4 "18.4.89.46")
> (define bayfront-ip4 "185.233.100.56")
> (define berlin-ip4 "141.80.181.40")
> +(define milano-guix-1-ip4 "159.149.133.203")
>
> (define-zone-entries guix.gnu.org.zone
> ;; Name TTL Class Type Data
> @@ -89,6 +90,7 @@
> ("issues" "" "IN" "A" berlin-ip4)
> ("logs" "" "IN" "A" bayfront-ip4)
> ("ci" "" "IN" "A" berlin-ip4)
> + ("data" "" "IN" "A" milano-guix-1-ip4)
>
> ;; This record is required in order to prove to Amazon ACM that we
> ;; own the domain. As long as it exists, ACM will automatically
> @@ -102,4 +104,4 @@
> (zone (zone-file
> (origin "guix.gnu.org")
> (entries guix.gnu.org.zone)
> - (serial 2019090201)))))
> + (serial 2019090601)))))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2019-09-06 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 11:44 [bug#37320] [PATCH] hydra: dns: Add "data" to point at milano-guix-1 Christopher Baines
2019-09-06 13:10 ` Christopher Baines [this message]
2019-09-06 22:04 ` Ludovic Courtès
2019-09-07 19:29 ` bug#37320: " Christopher Baines
2019-09-08 20:03 ` [bug#37320] " Ludovic Courtès
2019-09-08 20:23 ` Christopher Baines
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7bhbmfd.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=37320@debbugs.gnu.org \
--cc=guix-sysadmin@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).