matthew - retroedge.tech on Nostr: Anybody else seeing DNS issues today where PTR records for email reverse DNS lookup ...
Anybody else seeing DNS issues today where PTR records for email reverse DNS lookup were working fine earlier this week and now are not?
Seeing that with one of the email servers I take care of on all the domains. Nothing in the mail server configuration has changed and reverse DNS lookups were working fine earlier this week.
I am not sure what changed. Any suggestions on what to look for?
INCOMING CONNECTION FROM 208.28.90.24...
I am unable to determine the hostname associated with IP address 208.**.**.**. To avoid deliverability issues, you should set up a PTR record for your IP.
208.**.**.**.
#DNS #email #sysadmin
Published at
2024-03-21 18:35:50Event JSON
{
"id": "73c4921c4412a7010b6e3d94e4579c8ed18bc89748633514c3fa30f7ee71ad80",
"pubkey": "7bd696c00fbaa3d24d7303bb36c0ae39a1f355aa5f956b2a574c7da4297d59b4",
"created_at": 1711046150,
"kind": 1,
"tags": [
[
"t",
"dns"
],
[
"t",
"email"
],
[
"t",
"sysadmin"
],
[
"proxy",
"https://social.retroedge.tech/objects/fc7f8d64-433a-4d9c-9a82-41e64d1148d4",
"activitypub"
]
],
"content": "Anybody else seeing DNS issues today where PTR records for email reverse DNS lookup were working fine earlier this week and now are not? \n\nSeeing that with one of the email servers I take care of on all the domains. Nothing in the mail server configuration has changed and reverse DNS lookups were working fine earlier this week. \n\nI am not sure what changed. Any suggestions on what to look for? \n\nINCOMING CONNECTION FROM 208.28.90.24...\n\nI am unable to determine the hostname associated with IP address 208.**.**.**. To avoid deliverability issues, you should set up a PTR record for your IP.\n\n208.**.**.**.\n\n#DNS #email #sysadmin",
"sig": "149e5b95761772dad2e36fd2c9ab6d21748ee47e10489ecda86f008649f32e8119ec78387e182f116668ec12a17e22ed1a9981db5a090c227db524b6aeb79273"
}