TXT record Puns

So I have a CNAME record: login.example.com -> auth.com which works but our customer is requesting a TXT record for verification of DNS.

I don't know exactly what they're asking for and I'm not sure how I should go about doing this, anyone able to point to the right direction?

Preface: I just took over IT for a friend's company. I'm comfortable with Google Workspace/GSuite and very familiar with public DNS in general. They are expanding into a slightly different line of business and for this we are adding a second domain to the Google Workspace and a simple website to go along with it.

TL;DR: How do I add a Google Workspace verification TXT record in DNS after someone apparently deleted it years ago? Is it even necessary if things are working fine? How often does Google re-verify the domain?

I built a fresh website and while looking through DNS records that the previous admin set up, I noticed we have no TXT record for domain verification on the original domain. The domain and Gsuite have been in use for at least 5 years now and everything is working just fine. When I added the second domain, I set up the verification TXT record and emails/other functions are working just fine. Is there a way to regenerate or view the TXT record for the original domain? Is it the same as the new domain I added? Am I worried about nothing?

Lately we have been seeing services like Apple Business Manager and the Google Web Reporting tools requiring you to add a TXT record to DNS to provide verification of domain ownership (apple-domain-verification=RaNdOmLeTtErSaNdNuMbErS ). Is this a one time process, so once the verification has been done we are free to delete TXT record or are they going to check for the entry periodically?

Wow. We just started getting some email delivery failures reported by our customers, and when we checked MX Toolbox found our SPF records hosted in Route53 were dead/corrupted.

I peaked in and we have literally dozens of broken TXT records!

Expected multiline Route53 TXT record format: "v=spf1 a mx include:_spf.google.com ~all"

Actual (without our intervention): "v=spf1" "a" "mx" "include:_spf.google.com" "~all"

Did some sort of automated parser at Route53 completely fail? All of a sudden we have all of these formerly single line records broken into multiline records by their whitespace.

This is having a HUGE impact on our companies.

I'm trying to verify ownership of my domain so I can use AD connect but I don't want our emails to go to office 365.

Can anyone confirm that TXT records are only used for verification and I would still need to use MX to start forwarding emails? I was pretty sure I saw somewhere in the docs that an MX record would automatically be created after verification, but I can't find the page now.

Thanks!

Edit: Just an update. Domain verification was successful (after some other complications). Emails are all still working. Now onward to Active Directory Connect! Fingers crossed that goes smoothly. I've been pretty darn impressed with how easy it has been to use Azure's migration utilities thus far. Thanks for the input everyone. Sometimes documentation just isn't enough.

Hey guys, I'm listing a domain at GoDaddy and adding the text record in my cPanels DNS editor, but next to the text record it asks for "valid zone name".

It won't let me put the @ symbol and GoDaddy support didn't even seem to know what an auction is.

Can anyone point me in the right direction?

I'm a little unclear how or where I'm supposed to properly add DNS records when using a 3rd party DNS server.

• Domain: On namesilo (default DNS is dnsowl). However, I'm pointing that DNS to the one recommended by my webhost, let's call it 3rdpartydns.com
• Web host: A shared webhost with WHM/Cpanel setup and a number of accounts.

I'm trying to configure Zohomail to work with my domain, but need to add a TXT record for verification and change MX records.

Within name silo, if I try to add records there, it indicates that they will not take any effect because I am using a 3rd party DNS server.

1. In general I've always been a little unclear on why web hosts require me to use their own DNS server. Why is this generally needed? Can't google or domain provider DNS servers index sites already? Just a speed of DNS update type thing and it all cascades down?

2. I've emailed my web host, but while waiting, do you typically know in general where on a shared host you would add/edit records for their DNS on a per-domain basis? I see a 'dns zone template' editor within WHM which edits a text file, but not sure where else I would look in whm or cpanel to edit domain records.

Thanks!

I spruce up workshops hosted in Zoom and it would be really cool to have a space in the frame for the chat messages that come through.

The messages are saved as a .txt file in this format:

00:00:00 Screen Name: Message

Is there a service that turns that kind of information into a subtitle file?

Any breakthroughs are appreciated.

Hey, is there any way to add SSL to a domain without having to add a TXT record to the DNS of the domain?

My Let's encrypt cert is invalid and I cannot renew it, because my hosting provider has a bug that doesn't let me change the DNS settings of the domain. I cannot reach their support for hours now, my website is down and users are angry.

Hello /r/sysadmin! - I have lurked here for SO many years but I believe this is my first post.

I have a subdomain with a CNAME setup. I need to add a TXT record for a verification with Google Cloud. While I understand this is technically not supported because of RFC1034 most NAMESERVER hosts seem to allow it. The issues is, I've come across an Infoblox server that does not allow this.

According to this link there is a way around it using --txt-prefix but I have no idea how to implement this. I've searched Google for --txt-prefix and I come across many posts saying it's the solution and that said flag exists but none that say how to apply said flag. I'm hoping someone can help me figure out how to make my needed TXT and CNAME live together in harmony...or at least look like they do when a DNS request is made.

When we add multiple custom domains to tutanota, the txt verification records "t-verify=****" are the same for all domains added to the account. I read in one of the earlier threads that we are supposed to keep the txt record intact since tutanota has to verify it periodically. So each account has a unique txt record that can easily be tracked across domains as long as you use tutanota.

If I have appledomain.com and orangedomain.com, since they both have the same txt record if you query the dns records, they can easily be linked and becomes a privacy issue.

Our domain currently has the following SPF TXT record:

Name = @; Type = TXT; Value = v=spf1 include:_spf.google.com ~all

A vendor we work with needs us to put the following record on our domain:

Name = @; Type = TXT; Value = 43lm623laslj43ll

When I tried to do that, Google Domains would not allow me to and said that the "record is already in use."

In order to solve this issue, can I change the name of our existing SPF TXT record from "@" to "SPF" without issue?

Can the name of the existing SPF TXT record be changed to any random alphanumeric? Or, are SPF validator programs trained to only look for "@" name TXT records?

Hi.

Last week, u/ocelost posted about my dynamic dns server here. Many of you upvoted request made by u/lyrajc and u/Nolzi to add the ability to edit TXT records for you dynamic domains. I'm happy to announce that I have implemented it, and it would be great if you could find some time to try and test it. (It's not announced yet on my website, and I consider it a beta feature for now).

The new parameter name is &txt=

For example:

https://freemyip.com/update?token=YOUR_TOKEN&domain=domain.freemyip.com&txt=my%20test%20text

Then from a Linux host, you can use this to see it:

$ host -t TXT domain.freemyip.com 
domain.freemyip.com descriptive text "my test text"

It will also automagically work for any subdomain within your domain, eg:

$ host -t TXT blahblah.domain.freemyip.com

If you want to remove your TXT record, do this &txt=null

You can also add parameter &verbose=yes to see some more information in the output, especially if you encounter an error.

Any time you change anything, you will have to wait around 1 minute for DNS cache to get updated.

If you have any questions, or if you encounter any issues, please let me know.

I previously had this working before a MicroSD Card failure caused me to upgrade my card and install PiHole from scratch again.

I have TXT records, PTR records and srv-host records for an AirPrint setup to allow for remote printing.

Is there any way to get this going on PiHole 5+ or do I need unbound?

Thanks!

Hi, Folks!

I have a mystery TXT record in my DNS. Looks like "MS=D9623B407xxxxxxxxxxyyyyyyyyyyzzzzzzzzzzE".

I know ms=msXXXXXXXX -- any chance the above syntax (literally 40 chars long) is just a REALLY old Ms-O365 format?

Thought I'd ask before scream testing it.. by deleting.

Thanks!

So I have a CNAME record: login.example.com -> auth.com which works but our customer is requesting a TXT record for verification of DNS.

I don't know exactly what they're asking for and I'm not sure how I should go about doing this, anyone able to point to the right direction?