rolisteam.org is not a valid domain name to commit on git.
Closed, ResolvedPublic

Description

The rolisteam.org is managed by kde and my git config set "renaud AT rolisteam.org" as email address. The mail server is hosted on my own server.
When I commit I get this log:

remote: Audit failure - Commit bc6bd216d934be3e15f53eabe25051afb0251 - Email address has an invalid domain : renaud AT rolisteam.org

Is there a way to fix that ?

Regards

renaudg created this task.Apr 5 2020, 12:25 PM
Restricted Application added a subscriber: sysadmin. · View Herald TranscriptApr 5 2020, 12:25 PM

I think for git you should use a proper @ character, so renaud@rolisteam.org, since I could not find any handling for "AT" in the audit script (https://github.com/KDE/repo-management/blob/a2bf51330a735f29efaff31e5b2d9a8342069c72/hooks/hooklib.py#L490)

Yes, that's not even an email address :)

Looks like we don't have anything to correct here?

renaudg added a comment.EditedApr 6 2020, 11:22 PM

I used AT in order to obfuscate my address here on the ticket report, but yes in my git config I have a proper address with an @.

The error message is : "Email address has an invalid domain", and not Email address is invalid.

Turns out this is a DNS problem. The domain's NS records (in the registrar) point to both OVH and cloudns.net:

$ dig rolisteam.org ns @b0.org.afilias-nst.org.
[...]
;; AUTHORITY SECTION:
rolisteam.org.          86400   IN      NS      pns31.cloudns.net.
rolisteam.org.          86400   IN      NS      dns103.ovh.net.
rolisteam.org.          86400   IN      NS      pns33.cloudns.net.
rolisteam.org.          86400   IN      NS      ns103.ovh.net.
rolisteam.org.          86400   IN      NS      pns32.cloudns.net.
rolisteam.org.          86400   IN      NS      pns34.cloudns.net.

ovh.net doesn't have the MX record:

$ dig rolisteam.org mx @dns103.ovh.net.
[...]
;; QUESTION SECTION:
;rolisteam.org.                 IN      MX

;; AUTHORITY SECTION:
rolisteam.org.          300     IN      SOA     dns103.ovh.net. tech.ovh.net. 2019062216 86400 3600 3600000 300

Thus, when the recursive nameserver hits cloudns.net, it gets the MX record. When it hits ovh.net, it doesn't. From my computer:

$ dig rolisteam.org mx | grep 'ANSWER\|MX'
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;rolisteam.org.                 IN      MX
;; ANSWER SECTION:
rolisteam.org.          1631    IN      MX      10 mail2.rolisteam.org.

$ dig rolisteam.org mx | grep 'ANSWER\|MX'
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;rolisteam.org.                 IN      MX

$ dig rolisteam.org mx | grep 'ANSWER\|MX'
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;rolisteam.org.                 IN      MX

$ dig rolisteam.org mx | grep 'ANSWER\|MX'
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;rolisteam.org.                 IN      MX
;; ANSWER SECTION:
rolisteam.org.          1241    IN      MX      10 mail2.rolisteam.org.

$ dig rolisteam.org mx | grep 'ANSWER\|MX'
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;rolisteam.org.                 IN      MX
;; ANSWER SECTION:
rolisteam.org.          1240    IN      MX      10 mail2.rolisteam.org.

I assume the same is happening from KDE's git server. If you run git push, and when the hooks do the DNS resolution it happens to contact the OVH nameserver, it will see the domain has no A or MX record and fail.

Workaround: retry git push a few times and it should eventually work.
Fix: this is your domain so remove the OVH nameservers :)

nalvarez assigned this task to renaudg.Apr 7 2020, 12:45 AM

(I think it's the first time I get to assign a ticket back to the reporter :D)

I'm not sure I can.

renaudg closed this task as Resolved.Apr 7 2020, 8:39 AM

You've found the option to remove the OVH nameservers I gather?

I close the ticket because you can't do anything, on the ovh side, the site is bad, I try to remove and the change fails. I ask to the OVH support, and they say It fails because I have to clean up the server list first, then add the cloudns from KDE.

I believe the issue is in OVH's web site. I will try to do what the OVH support guys said but, I think it may cause access issue for a while.

Okay, thanks for confirming that!