email routing gone wrong(?)

[graceful warren]

Hey there!

I've been using email forwarding for almost a year without any problem, but recently I noticed that newly created domain email doesn't send anymore to my gmail account. Is there any reason why did that happen?

*it says that my domain/email address does not exist everytime sending to the domain email

[obsidian sundial]

Hey,
What's the domain, and what is the exact error you get? Any more details on the exact error would be helpful, usually you get a error code.
If it's a new address/route you added, sometimes it takes a bit for it to sync. On the Email Routing Overview page, it will show "Routing Status", if it says syncing it's not done yet. I've had it take a solid few minutes before.

[graceful warren]

Let me get a screenshot real quick

here you go

so, basically I've done with all spf, dkim and mx records

I've also set up the email which to receive the forwarded emails

The thing is, on my older domains which I have made like more than half a year ago worked just fine

[obsidian sundial]

Interesting, how long ago was that test from? The MX records appear to exist now

[graceful warren]

I tested it just now

I've been trying to resolve the issue since yesterday

I thought waiting for SSL would solve the issue, but no

I tried with my other domain which I have already been using over the year, the alias email worked fine

Until I create a new one and tried it

it didn't work

I've seen people in the forum talking about gmail "blocking" forwarded emails from cloudflare, but I don't know exactly what happened. So I came here

[obsidian sundial]

yea ssl isn't related sadly, it's saying it cannot find the MX Records for your domain, even though they seem to exist fine: https://mxtoolbox.com/SuperTool.aspx?action=mx%3Amizu2.my.id&run=toolpage
It could be something as simple as dns cache google has, but that seems like a long time. I just tried sending a test email as well, will see if it bounces

[graceful warren]

Oh, I received your email

[graceful warren]

I tried using other gmail accounts to send dummy mails to my alias domain email right, it also gave me such error

[obsidian sundial]

oh, I think I can start to see why, it looks like Google's DNS doesn't see that record

[graceful warren]

Mmhm, and I saw some cases in the community forum. Some had their emails forwarded, but not received in their receiving emails

some had the same error with mine

[obsidian sundial]

The gmail thing is different, and you would be able to see it under Email routing summary -> activity log

[graceful warren]

let me check it real quick

[obsidian sundial]

yea, it would show as the emails actually being rejected (delivery failed) in there

[graceful warren]

no, i guess?

[obsidian sundial]

it looks like it did forward one of your emails from that page

[graceful warren]

it's a success I believe

[obsidian sundial]

but yea that looks fine, the DNS issue you are hitting with gmail is them not making to CF Email Routing at all, makes sense it wouldn't show the failures there

[graceful warren]

so, what do I do

is there any solution? or it's just gmail thing

[obsidian sundial]

It looks like the root cause is Google DNS does not see your domain as existing at all
https://dns.google/query?name=mizu2.my.id&rr_type=MX&ecs=

not sure how new it is, ccTLDs are a bit slower/weird sometimes

[graceful warren]

it's... not?

i have some ccTLD domains prior to this one

they're working fine right now, since I made the alias email like months ago

[obsidian sundial]

.id is a ccTLD
https://en.wikipedia.org/wiki/.id

but regardless that's just speculation, the root cause is something to do with Google not being able to lookup the nameservers of your domain from one of the .id nameservers

[graceful warren]

so it's on Google's end

Mhmm... might as well wait until I get a solution to this

[obsidian sundial]

eeh I would say it's more likely to be on my.id's end. It looks like that domain is kind of new, and that one of the authoritive nameservers for my.id is just not returning the nameservers for it

[graceful warren]

I'm pretty sure it isn't really new though

my other domain, miraaaa.my.id

worked fine

it's still able to receive the forwarded emails

[obsidian sundial]

DNS is all off the idea of delegation, the root nameservers say "ask x for id nameservers", "ask y for my.id nameservers" "ask z for mizu2.my.id", that last one is failing.
Google is saying that b.dns.id, one of the nameservers for my.id, is returning nxdomain

[graceful warren]

but, newly created alias didn't work

[obsidian sundial]

According to whois mizu2.my.id was created yesterday
Domain Name: mizu2.my.id
Created On: 2023-06-15 11:09:06
That's what I thought it was brand new

[graceful warren]

Uh let me make sure

you meant mizu2.my.id is newly created right

not .my.id ?

I'm sorry, my grammar isn't really good

I may not understand easily

so, I'll just have to wait then

[obsidian sundial]

yes

[graceful warren]

thank you for the help and explanation, Chaika

[obsidian sundial]

Sure, ccTLDs just tend to be the most flakey/weird from my experience, I can't even get two of their rnameservers to respond (although some do block direct like that on purpose)

[graceful warren]

got it 👍