Closed Bug 1050313 Opened 10 years ago Closed 10 years ago

restmail.net not reachable anymore

Categories

(Infrastructure & Operations :: SSL Certificates, task)

Product:
Infrastructure & Operations
Component:
SSL Certificates
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: whimboo, Assigned: cturra)

References

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/705] ) 

Since a couple of days the domain restmail.net is no longer accessible. Checking for nameserver entries shows that the domain entries are misconfigured.

I'm not sure if this domain recently got transferred to Mozilla or not, but we were using the restmail service on it for testing Firefox Accounts with dynamically created email addresses.

Our tests are currently broken due to this problem. So it would be good if someone could have a look at this domain.
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/705]
this domain is not owned by us and i cannot track down any hosting on our end either. i'd recommend reaching out to the domain owner for further details.

 $ whois restmail.com | grep Registrant
 Registry Registrant ID:
 Registrant Name: M.M. Obuhov
 Registrant Organization:
 Registrant Street: Moscow
 Registrant City: Moscow
 Registrant State/Province: Moscow
 Registrant Postal Code: 82410
 Registrant Country: Russian Federation
 Registrant Phone: 21614433
 Registrant Phone Ext:
 Registrant Fax:
 Registrant Fax Ext:
 Registrant Email: operhost@gmail.com


* you mentioned a domain transfer to mozilla in your bug - i don't see a bug (open or complete) for that either. 

i am marking this bug as r/invalid since there is nothing we (webops) can action on this bug.
Assignee: server-ops-webops → cturra
Status: NEW → RESOLVED
Closed: 10 years ago
OS: Linux → All
Resolution: --- → INVALID
You are using the wrong domain. It is .net and not .com.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
chris:

restmail.net was the domain filed about, not .com

restmail.net appears to be owned by mozilla
doh. sorry about that!

right now the following ns servers are configured. you've indicated these are not correct, but i don't have any record of what they should be changed to? 

note: i just had a look at this domains record in our registrar and the ns records have not been updated since the domain transfer completed on july 1st.

  $ whois restmail.net | grep "Name Server: N"
   Name Server: NS1.IWANTMYNAME.NET
   Name Server: NS2.IWANTMYNAME.NET
   Name Server: NS3.IWANTMYNAME.NET
   Name Server: NS4.IWANTMYNAME.NET
Flags: needinfo?(tom)
This was transferred to us in bug 1030841. I suspect this is something run by Cloud Services? No idea why they're using that particular NS host.
:gene is contacting lloyd the previous owner.
Depends on: 1050379
The NS records have been transferred. How just waiting for TTLs to expire and the service will be back up.
It's interesting because the domain was still working at least until July 16th, when we did a TPS testrun for the 31.0 release of Firefox. So something has been changed in the last couple of days. Someone on IRC said, that this domain was working even yesterday.
Gene, thanks! Shall we also check all the other domains which have been transferred if they are also affected?
:whimboo yup, that's what I did in Bug 1050379
> It's interesting because the domain was still working at least until July 16th, when we did a TPS testrun for the 31.0 release of Firefox. So something has been changed in the last couple of days. Someone on IRC said, that this domain was working even yesterday.

:whimboo, what happened is that we transfered ownership of the domain to Mozilla a month or so ago. I then asked Lloyd to send me the DNS zone for the domain so I could recreate it in AWS route53. He never got back to me and yesterday his registrar, which no longer controlled the domain name, cleaned up their DNS servers and deleted the old zones.

I reverse engineered what I could of the now lost zone files from the AWS console.
:cturra

err... I don't know anything. whimboo was on IRC looking for help, and I picked it up

Looks like it's sorted now anyways
Flags: needinfo?(tom)
thnx to the work done by :gene and :digi, this should be resolved as soon as DNS propagation is complete (could take a bit since it appears as the old NS records didn't have a short TTL). in the mean time, i am going to mark this bug as r/fixed.

 $ whois restmail.net | grep "Name Server: N"
  Name Server: NS-1527.AWSDNS-62.ORG
  Name Server: NS-1913.AWSDNS-47.CO.UK
  Name Server: NS-236.AWSDNS-29.COM
  Name Server: NS-590.AWSDNS-09.NET

 $ dig +short @NS-1527.AWSDNS-62.ORG restmail.net
 174.129.3.62
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
It works fine again. Thanks for the quick turnaround!
Status: RESOLVED → VERIFIED
Sorry, but not everything is working for that domain. The most important part, which is receiving emails, is dead. I tried to send an email to mozilla-tps-ci@restmail.net, but that is never appearing. Is the mail server down, or does it need a restart?
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
To add, here the URL where the email should appear: https://restmail.net/mail/mozilla-tps-ci@restmail.net
:whibmoo, I can confirm restmail is working (receiving and surfacing emails through the REST interface). You can see it responding over SMTP here

http://mxtoolbox.com/SuperTool.aspx?action=smtp%3arestmail.net&run=toolpage

The cause of what you're seeing is very likely that your Mail Transfer Agent still has the NXDOMAIN cached from yesterday. It'll just take time for this service to become available globally.

What mail server are you using to send the email?
And here are details showing that DNS is correct, it's just that some servers out that have cached NXDOMAIN values :

2014-08-08 09:46:02 ✔ gene@ruth ~$ dig net NS +short
j.gtld-servers.net.
c.gtld-servers.net.
g.gtld-servers.net.
a.gtld-servers.net.
h.gtld-servers.net.
e.gtld-servers.net.
k.gtld-servers.net.
d.gtld-servers.net.
f.gtld-servers.net.
b.gtld-servers.net.
m.gtld-servers.net.
l.gtld-servers.net.
i.gtld-servers.net.
2014-08-08 09:46:05 ✔ gene@ruth ~$ dig restmail.net NS @i.gtld-servers.net.

; <<>> DiG 9.9.5-3-Ubuntu <<>> restmail.net NS @i.gtld-servers.net.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4447
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;restmail.net.			IN	NS

;; AUTHORITY SECTION:
restmail.net.		172800	IN	NS	ns-236.awsdns-29.com.
restmail.net.		172800	IN	NS	ns-590.awsdns-09.net.
restmail.net.		172800	IN	NS	ns-1913.awsdns-47.co.uk.
restmail.net.		172800	IN	NS	ns-1527.awsdns-62.org.

;; ADDITIONAL SECTION:
ns-236.awsdns-29.com.	172800	IN	A	205.251.192.236
ns-590.awsdns-09.net.	172800	IN	A	205.251.194.78

;; Query time: 142 msec
;; SERVER: 192.43.172.30#53(192.43.172.30)
;; WHEN: Fri Aug 08 09:46:09 PDT 2014
;; MSG SIZE  rcvd: 210

2014-08-08 09:46:09 ✔ gene@ruth ~$ dig restmail.net MX @ns-236.awsdns-29.com. +short
10 restmail.net.
2014-08-08 09:46:13 ✔ gene@ruth ~$ dig restmail.net A @ns-236.awsdns-29.com. +short
174.129.3.62
2014-08-08 09:46:15 ✔ gene@ruth ~$
For testing I was using my mozilla.com account. And it is still not working. When I send an email it does not appear in the web interface. Also I don't get a bounce or failure back. Sending the email directly by logging into restmail.net via telnet works.
This would be because the mozilla mail server's local nameserver has a cached nxdomain value. Sending from mozilla mail servers to restmail.net will continue to fail until it's local nameserver's cache value for restmail.net expires. The same will also be true for other mail servers out on the internet which have local nameservers with the cached nxdomain.
i am going to close this as r/fixed again since this is in fact sorted minus so caches expiring. 

:whimboo - if you continue to have mail delivery issues, can you please open a new bug to address just that issue?
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Meanwhile all is working fine and my sent emails from Friday have been delivered. Also emails I send now, are getting directly delivered. So as Gene said, it was our mail server, which had the old address in the cache.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.