#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+-----------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Keywords:
--------------------------+-----------------------
As reported in #2306 (Forum service - Discourse) – OSGeo and in
#2306 (Forum service - Discourse) – OSGeo there are at least 2
name servers from internet service providers (ovh.net and ehiweb.it) that
do now know (after 7 days) about the existance of an MX record for
discourse.osgeo.org
I suspect there is something to improve from our side to make propagation
of these records faster.
I confirm clearing caches (like installing a new nameserver and using it
from scratch) is able to see the MX record, so it is a matter of cache
lifetimes.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3068>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Changes (by strk):
* cc: discourse (removed)
* keywords: => discourse
--
Ticket URL: <#3068 (MX record for discourse.osgeo.org is not propagating properly) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Comment (by strk):
My (new) server and my desktop client are still not getting the MX record
for discourse.osgeo.org as of today. Was the zone version updated ?
--
Ticket URL: <#3068 (MX record for discourse.osgeo.org is not propagating properly) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Comment (by strk):
It would be nice to put the DNS zone under Ansible too...
--
Ticket URL: <#3068 (MX record for discourse.osgeo.org is not propagating properly) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Comment (by strk):
Even osgeo7 resolver isn't getting the MX record at the moment:
{{{
tech_dev@osgeo7:~$ nslookup
> set type=mx
> discourse.osgeo.org
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
discourse.osgeo.org canonical name = web.osgeo9.osgeo.org.
Authoritative answers can be found from:
>
}}}
--
Ticket URL: <#3068 (MX record for discourse.osgeo.org is not propagating properly) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Comment (by strk):
I see no output from these commands:
{{{
dig @213.186.33.99 -t mx discourse.osgeo.org| grep 'MX' | grep -v '^;'
dig @2001:41d0:3:163::1 -t mx discourse.osgeo.org| grep 'MX' | grep -v
'^;'
}}}
Both addresses are from ovh.net
The ehinet addresses wont' respond from the outside
--
Ticket URL: <#3068 (MX record for discourse.osgeo.org is not propagating properly) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Comment (by strk):
May be cloudflare related:
https://community.cloudflare.com/t/mx-record-didnt-updating/353209
--
Ticket URL: <#3068 (MX record for discourse.osgeo.org is not propagating properly) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Changes (by robe):
* Attachment "cloudflareconfig.png" added.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3068>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Comment (by robe):
Replying to [comment:6 strk]:
> May be cloudflare related:
> https://community.cloudflare.com/t/mx-record-didnt-updating/353209
The person on that ticket made two mistakes
1) They tried to put in the name of their domain which ends up doing
something silly like
mydomain.com.mydomain.com
2) They used Proxy instead of DNS only
By contrast ours looks like this:
[[Image(cloudflareconfig.png)]]
so this has nothing to do with our problem.
I'm also puzzled why it's not every dns in the world having this issue
with our setup.
Did those admins tell you what the upstream problem is? If they didn't
give specifics, I'd assume they are just trying to pass on the problem to
someone else cause they have no clue.
--
Ticket URL: <#3068 (MX record for discourse.osgeo.org is not propagating properly) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3068: MX record for discourse.osgeo.org is not propagating properly
--------------------------+------------------------
Reporter: strk | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Unplanned
Component: SysAdmin/DNS | Resolution:
Keywords: discourse |
--------------------------+------------------------
Comment (by robe):
I forgot to show the config of meet.osgeo.org in that screen shot.
{{{
A meet 140.211.15.5 DNS only
}}}
But anyway I can't replicate the issue on any of the servers I have access
to or any of the MX checkers I have tried online. I tried the below:
{{{
host -t mx discourse.osgeo.org
}}}
on an amazon server, atlantic.net, osuosl.org server, my comcast.net
and all report
{{{
discourse.osgeo.org mail is handled by 1 meet.osgeo.osuosl.org.
discourse.osgeo.org mail is handled by 10 meet.osgeo.org.
}}}
I also tried -
Network Tools: DNS,IP,Email
and it came back with the same answer in addition to whining about not
having a DMARC policy which is a separate issue.
--
Ticket URL: <#3068 (MX record for discourse.osgeo.org is not propagating properly) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.