How to ask us to change a DNS record
Open a Website Support ticket in the client portal, name the domain, and paste the exact record type, name and value you need, plus what it's for. We make the change in Cloudflare and reply when it's done.
Applies to: Cloudflare Oogle client portal
On this page
To add or change a DNS record for a domain on Oogle hosting, open a Website Support ticket in the client portal with the domain, the record type, the exact name and value, and what it's for. We make the change in Cloudflare, where your DNS is managed, and reply in the ticket when it's done. There's no self-service DNS editing yet.
Before you start
- Find the record details the service gave you. Verification pages and email setup pages usually list the type, name (or host) and value (or content, target or points to). Keep that page open.
- If the change could affect your website or email, such as replacing MX records or pointing the bare domain elsewhere, read Change DNS without taking your website or email offline first.
Open the ticket
- Sign in at my.oogle.net.
- Go to Support Departments.
- Choose Website Support.
- In Summary, write what you need, for example "Add Google verification TXT record for example.com".
- Choose a Priority. A routine record is not an emergency; a record that has stopped your email or website working is.
- In Related Service, choose the service for the website on that domain.
- In Details, give the information listed below.
- Select Open Ticket.
What to put in Details
- The domain, for example
example.com. - What the record is for: "verify our domain with Microsoft 365", "send newsletters from Mailchimp", "point
shop.example.comto our store". - Each record, copied exactly: its type (A, AAAA, CNAME, MX, TXT or CAA), its name or host (
@for the domain itself, or a subdomain such aswwwor_dmarc), its value or target, and for MX records its priority. - Add or replace: whether this adds to existing records or replaces them. If replacing, say which.
- Any deadline, such as a launch date, so we can plan with you.
A ready-to-copy example:
Domain: example.com
Purpose: Verify the domain with our email provider
Type: TXT
Name: @
Value: provider-verification=abc123example
Add or replace: AddIf the service gives you a screenshot instead of text, attach it, but please also paste the values as text so nothing is mistyped.
What never goes in a ticket
Never include a password, an API key, a one-time code or a sign-in link for any service. DNS values are fine to share; credentials aren't.
What we do
We check the request against your existing records (for example, a new SPF value is merged into your existing SPF record rather than added as a second one), make the change in Cloudflare, set proxy status where it applies, and reply in the ticket. If something in the request would break another service, we'll ask before going ahead.
You'll know it worked when
We reply that the change is made, and the service that asked for it reports success when you select its verify button. Proxied records update in about 5 minutes; DNS-only records may take up to their TTL. To check yourself:
dig txt example.com +shortReplace txt with the record type and example.com with the name. The new value should appear. Without a command line, enter the name at Google Public DNS, select Resolve, and choose the record type.
Troubleshooting
- The service still says "not found". Wait a little, then check the name. Some services show the name with your domain already on the end; entering it again creates
name.example.com.example.com. Reply to the ticket with what the service shows. - You're not sure which record a service needs. Send us the link to its setup instructions.
- Something stopped working after the change. Reply on the same ticket straight away, with what stopped and when.
- Your ticket was closed before you could check. Tickets close automatically after 3 days without your reply. Open a new one and mention the old ticket number.
Next steps
- DNS records explained
- How to open a support ticket
Frequently asked questions
Why can't I change my DNS myself?
Your domain's DNS is in Oogle's Cloudflare account, and there's no self-service DNS editing yet. A DNS editor in the client portal is planned. Until then, we make changes on request.
Is it safe to paste DNS values into a ticket?
Yes. DNS records are public once published, so the values aren't secret. Never paste a password, an API key or a login link.
Can I ask for several records at once?
Yes. List them all in one ticket, especially when they belong to the same setup, such as a new email provider.
Can I phone instead?
Use a ticket for DNS changes so the exact values are written down. Copying long values by phone invites mistakes.