freenetname - no MX or A record - error using webmail

[#1]

Plusnet have paid the bill!

And until 2029 too.

----------------------------------

Domain name:
freenetname.co.uk

Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 10-Dec-2012

Registrar:
Plusnet Plc t/a Madasafish Broadband [Tag = MADASAFISH]
URL: http://www.madasafish.com

Relevant dates:
Registered on: 26-Jul-1999
Expiry date: 26-Jul-2029
Last updated: 27-Aug-2019

Registration status:
Registered until expiry date.

Name servers:
ns1.force9.net
ns2.force9.net

WHOIS lookup made at 11:17:21 27-Aug-2019

[#2]

I'm glad to see that this has been resolved now 

As this was flagged and resolved by the appropriate team, I hope that we won't have the same issue in another 10 years however and if I'm still around by then (:D) feel free to drop me a PM and I'll be happy to help.

Apologies again for the hassle this had caused.

[#3]

Hi,

Just checked mine and as with everyone else all is working now.

Many thanks to everyone involved.    

So what happens in 10 years time - do we need to remember to send a reminder?  

[#4]

@ndtqpr wrote:

Just checked mine and as with everyone else all is working now.

Many thanks to everyone involved.    

That's good to see, thanks for the confirmation. 

So what happens in 10 years time - do we need to remember to send a reminder?  

The domain shouldn't have been left to expire and this has been raised with the appropriate team internally to get to the bottom of the reason for this and ensure that this doesn't happen again in future.

[#5]

All up and running here as well. Thanks for the speedy resolution...

Wonder if we will have to nudge the IT team next year when are individual Domain names come up for renewal! 😎

[#6]

That's good to see and I'd hope that things will run smoothly moving forward.

We'll be investigating further and looking to put steps in place to try to ensure that's the case.

[#7]

I'll add my thanks to the team for sorting this out. I also discovered I'd 'lost' my freenetname account yesterday when I started getting pings from gmail (that automatically forwards my emails to the freenetname account) to say messages were not delivered as the domain could not be found. I then found that a number of my security systems, which were also linked to freenetname, had gone down as well.

When I finally got through to customer support they were quick to respond and my emails were up and running in quick time. Although no explanation was forthcoming at the time I'm glad to have found this discussion and equally glad you've put another coin in the meter!

[#8]

Thanks for the post @Shackman205 It looks like the adviser you spoke to raised your issue with an internal team this morning although about the same time as that our NetOps team resolved the issue on the back of this thread.

Sorry for the inconvenience this had caused, but I'm glad that it was quickly resolved following being reported to us.

If you need any further assistance please do feel free to let us know.