Assigned
Status Update
No update yet.
Comments
bl...@google.com
Automated by Blunderbuss job honestdns_tickets_blunderbuss_autoassigner for 2nd config honestdns_defects_customer_issues for component 191657.
ah...@google.com
Hello!
Our internal tool indicates this resolution issue is region-specific. When we query Google Public DNS internally for the domain you provided, all regions return valid answers except for the GRQ (Netherlands) region. Queries from that region for this domain return an NSTIMEOUT status code.
le...@gmail.com
OK, thanks.
The problem is intermittent from senders in the US. In 2023 we had issues
with 2 Google DNS servers 142.250.27.26 and 142.250.27.27.
Testing them now they are timing out. Is it possible to test each of your
DNS servers individually?
Leif
On Wed, Mar 5, 2025 at 6:51 PM <buganizer-system@google.com> wrote:
The problem is intermittent from senders in the US. In 2023 we had issues
with 2 Google DNS servers 142.250.27.26 and 142.250.27.27.
Testing them now they are timing out. Is it possible to test each of your
DNS servers individually?
Leif
On Wed, Mar 5, 2025 at 6:51 PM <buganizer-system@google.com> wrote:
le...@gmail.com
Today appeared another related problem with Google DNS servers. Emails that
we sent out were returned with these 2 messages:
Remote Server returned: '550 5.7.25 [75.103.70.193] The IP address sending
this message does not have a 5.7.25 PTR record setup, or the corresponding
forward DNS entry does not 5.7.25 match the sending IP. As a policy, Gmail
does not accept messages 5.7.25 from IPs with missing PTR records. For more
information, go to 5.7.25
https://support.google.com/a?p=sender-guidelines-ip 5.7.25 To learn more
about Gmail requirements for bulk senders, visit 5.7.25
https://support.google.com/a?p=sender-guidelines .
5b1f17b1804b1-43d0055c694si19181575e9.53 - gsmtp'
And:
Remote Server returned: '550 5.7.26 Your email has been blocked because the
sender is unauthenticated. 5.7.26 Gmail requires all senders to
authenticate with either SPF or DKIM. 5.7.26 5.7.26 Authentication results:
5.7.26 DKIM = did not pass 5.7.26 SPF [thepeoplelink.com ] with ip:
[75.103.70.193] = did not pass 5.7.26 5.7.26 For instructions on setting up
authentication, go to 5.7.26
https://support.google.com/mail/answer/81126#authentication
ffacd0b85a97d-3912c14d419si7510318f8f.882 - gsmtp'
Why are Google DNS servers not getting the correct data from our DNS
records? There is nothing wrong with them, but if there is, nobody else is
having a problem, so please advise what is going on here.
Thank you.
Leif
On Wed, Mar 5, 2025 at 6:51 PM <buganizer-system@google.com> wrote:
we sent out were returned with these 2 messages:
Remote Server returned: '550 5.7.25 [75.103.70.193] The IP address sending
this message does not have a 5.7.25 PTR record setup, or the corresponding
forward DNS entry does not 5.7.25 match the sending IP. As a policy, Gmail
does not accept messages 5.7.25 from IPs with missing PTR records. For more
information, go to 5.7.25
about Gmail requirements for bulk senders, visit 5.7.25
5b1f17b1804b1-43d0055c694si19181575e9.53 - gsmtp'
And:
Remote Server returned: '550 5.7.26 Your email has been blocked because the
sender is unauthenticated. 5.7.26 Gmail requires all senders to
authenticate with either SPF or DKIM. 5.7.26 5.7.26 Authentication results:
5.7.26 DKIM = did not pass 5.7.26 SPF [
[75.103.70.193] = did not pass 5.7.26 5.7.26 For instructions on setting up
authentication, go to 5.7.26
ffacd0b85a97d-3912c14d419si7510318f8f.882 - gsmtp'
Why are Google DNS servers not getting the correct data from our DNS
records? There is nothing wrong with them, but if there is, nobody else is
having a problem, so please advise what is going on here.
Thank you.
Leif
On Wed, Mar 5, 2025 at 6:51 PM <buganizer-system@google.com> wrote:
ah...@google.com
The error message describes what is wrong with your DNS records. Gmail requires that you have valid PTR and SPF records configured.
This problem may be specific to Google's very strict email validation requirements because other email providers may have less strict validation.
The links attached in the error message should be able to help with this.
le...@gmail.com
There is nothing wrong with my DNS records. I have checked them over, used
several different online tools and they all check out ok. Why is only Gmail
having a problem and can't find my DNS records? Can you check from your end
and see which of your DNS servers are returning bad data? Yesterday all our
emails were delivered with no bounces, today they are bouncing again. Is
there a cache that needs to be cleared to resolve? I really need this
fixed, it is a big problem. Thank you.
On Thu, Mar 13, 2025, 2:27 PM <buganizer-system@google.com> wrote:
several different online tools and they all check out ok. Why is only Gmail
having a problem and can't find my DNS records? Can you check from your end
and see which of your DNS servers are returning bad data? Yesterday all our
emails were delivered with no bounces, today they are bouncing again. Is
there a cache that needs to be cleared to resolve? I really need this
fixed, it is a big problem. Thank you.
On Thu, Mar 13, 2025, 2:27 PM <buganizer-system@google.com> wrote:
pu...@google.com
You may want to reach out to gmail support to ask if they are seeing specific issues exchanging email with your domain.
For DNS resolution of thethepeoplelink.com/MX record, we are seeing consistent timeouts in the Netherlands area. This could impact Western Europe area. If that correlates with your server locations, please check if you are blocking queries from our egress IPs as listed in https://developers.google.com/speed/public-dns/faq#locations_of_ip_address_ranges_google_public_dns_uses_to_send_queries .
For DNS resolution of the
le...@gmail.com
Ok, thanks. I thought this was Gmail support. Can I get the link to the
right support? We only work with people in the US so Netherlands is no
concern. I will check the DNS IPs.
Leif
On Fri, Mar 14, 2025, 7:59 AM <buganizer-system@google.com> wrote:
right support? We only work with people in the US so Netherlands is no
concern. I will check the DNS IPs.
Leif
On Fri, Mar 14, 2025, 7:59 AM <buganizer-system@google.com> wrote:
Description
DNS Error: 6119800 DNS type 'mx' lookup of