[Solved] Create DNS Records

[b0chard]

Good day!

I would like to add these list of DNS records for my account with the username of bochard:

CNAME Records

• webmail.tenkyuu.dev.    1    IN    CNAME    tenkyuu.dev
• www.tenkyuu.dev.    1    IN    CNAME    tenkyuu.dev

MX Records

• tenkyuu.dev.    1    IN    MX    0 johnny.heliohost.org

TXT Records

• _atproto.tenkyuu.dev.    1    IN    TXT    "did=did:plc:q74gsah26xz3q4qoe5ixx5jx"
• default._domainkey.tenkyuu.dev.    1    IN    TXT    "v=DKIM1; h=sha256; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+SDLc/Hl5PNixlC3Z1QqVI5F0WQUTC0wA2GHBtcHm+cqyRxqCWP7OmmV5Z7Vn3nos10c8TB7chpdkPiTVeO53mrpK6ZC9fjhlfFajdLReXJvRhqR+MBCwUEw1IimwFUz35YIRwqJ2bHaqvtjhuH4oOZ45qq79GB9gsc5OGC/A74pvZBOzMt1zYo" "3BvwUNo2LTgcyMDTu" "nY+ZU15PBFyE34tj8iniPctiznyx+MboWzR4FCG/igoSwuksUm591bW8PblllmtUzdIQi7ORn9P+JO+bCW29gJlJ77wxupzvelwUMbi/iNWrCnyVbJVNxHxGQTu4jzvMg74BfIGZ1YErmQIDAQAB;"
• _discord.tenkyuu.dev.    1    IN    TXT    "dh=f83b62898113aa75c72a4fa495f89c16fd7686e4"
• _dmarc.tenkyuu.dev.    1    IN    TXT    "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:mail@tenkyuu.dev; ruf=mailto:mail@tenkyuu.dev;"
• tenkyuu.dev.    1    IN    TXT    "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all"
• tenkyuu.dev.    3600    IN    TXT    "google-site-verification=gP9DbLrjLTsnPdCxCB4aFindIrtjQTovp2uVO5OX_Ec"

thank youu!!

[wolstech]

You're using Cloudflare so you have to do this yourself.

That said, the webmail and www CNAMEs exist already on our servers (they're standard) as well as the MX. The TXTs for the email stuff are generated by a script when you request SPF/DKIM/DMARC if you request email support, no need to supply values as our system generates them automatically. I've gone ahead and done this for you.

I especially did not use that DMARC record. You'd be hating yourself if I did...you'll be spammed to all hell by the automated reports (and probably end up suspended for disk space, the ruf can get you thousands of emails a day!), and your sent mail likely won't deliver on reject as most providers already have enough trouble accepting our mail without us telling them to throw it away...

This is your zone file on our side. You'll need to use our name servers though for it to actually do anything:

$TTL 14400
@      86400    IN      SOA     ns1.heliohost.org. heliohost4.gmail.com. (
                2025041701      ; serial, todays date+todays
                3600            ; refresh, seconds
                1800            ; retry, seconds
                1209600         ; expire, seconds
                86400 )         ; minimum, seconds

tenkyuu.dev. 86400 IN NS ns1.heliohost.org.
tenkyuu.dev. 86400 IN NS ns2.heliohost.org.


tenkyuu.dev. IN A 64.62.151.106
tenkyuu.dev. IN AAAA 2001:470:1:1ee::2009
ipv6 IN AAAA 2001:470:1:1ee::2009
tenkyuu.dev. IN MX 0 johnny.heliohost.org.

mail IN CNAME tenkyuu.dev.
www IN CNAME tenkyuu.dev.
ftp IN CNAME tenkyuu.dev.
webmail IN A 64.62.151.106
webmail IN AAAA 2001:470:1:1ee::2009

tenkyuu.dev. IN TXT  "google-site-verification=gP9DbLrjLTsnPdCxCB4aFindIrtjQTovp2uVO5OX_Ec"
_atproto.tenkyuu.dev. IN TXT  "did=did:plc:q74gsah26xz3q4qoe5ixx5jx"

tenkyuu.dev. 14400 IN TXT "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all"
_dmarc 14400 IN TXT "v=DMARC1; p=quarantine"
_domainkey.tenkyuu.dev. 14400 IN TXT "o=-"
default._domainkey.tenkyuu.dev. 14400 IN TXT ( "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+SDLc/Hl5PNixlC3Z1QqVI5F0WQUTC0wA2GHBtcHm+cqyRxqCWP7OmmV5Z7Vn3nos10c8TB7chpdkPiTVeO53mrpK6ZC9fjhlfFajdLReXJvRhqR+MBCwUEw1IimwFUz35YIRwqJ2bHaqvtjhuH4oOZ45qq79GB9gsc5OGC/A74pvZBOzMt1zYo3BvwUNo2LT"
"gcyMDTunY+ZU15PBFyE34tj8iniPctiznyx+MboWzR4FCG/igoSwuksUm591bW8PblllmtUzdIQi7ORn9P+JO+bCW29gJlJ77wxupzvelwUMbi/iNWrCnyVbJVNxHxGQTu4jzvMg74BfIGZ1YErmQIDAQAB;" )

 

[b0chard]

but, I already changed the nameservers from cloudflare to ns1.heliohost.org and ns2.heliohost.org since yesterday?

 

Edit: here is what shown in NS lookup.

would you please verify if I did it right?

thanks @wolstech!!

Edited 4 hours ago by b0chard

[wolstech]

Looks good if I check the actual DNS queries. Our admin tools still show (cloudflare) next to your domain which is why I said that.

There's probably a stale cache somewhere on our side, but that shouldn't impact the domain itself since public DNS is showing the right name servers...it's just a UI issue in our admin tools...