PlusNet / Force 9 TXT, SRV and Name Server ( NS ) Records

Posted by paris on Jan 24, 2012 in Random |

Further to my Easyspace post regarding TXT Updates , I tried to update TXT records for domain authentication for Office 365 on a new domain , however again, there was no where in plusnet’s manage DNS control panel to do this. A call on their support number, produced the fact they do not support TXT DNS Record updates.

Luckily in 365 there is another way to verify domain ownership which  is to use a low priority dummy MX record, which plusnet did allow. However … Microsoft utilise SRV records for Microsoft Lync to work. As Plusnet do not support these, or allow the changing of nameservers to Microsoft’s own ( Ns1.bdm.microsoftonline.com and Ns2.bdm.microsoftonline.com), I had to move the domain to 123-reg.co.uk a free transfer and allowed me to update the nameservers

All this would have been nice at : http://www.plus.net/support/hosting/domains/domain_admin_dns.shtml !

Tags: , , , ,

4 Comments

Nick
Jan 28, 2012 at 7:53 pm

Hi, I’m having the same problem trying to verify 365 with Plusnet but haven’t been able to get the MX record verification to work. Could you give some details of the MX record you entered at Plusnet?

Thanks

Nick


 
paris
Jan 29, 2012 at 1:10 pm

So there should be a drop down on the verification page “Select a verification method:”

Choose Add MX Record , it gives you the record e.g. :

@ ms25268857.msv1.invalid 1 Hour

At this at a higher priority than any of the other existing current MX Records e.g. 30


 
Nick
Jan 29, 2012 at 5:05 pm

I entered the MX record on Plusnet using the additional dns page, but it will not allow @ in the left field which I left blank, not sure if that’s important. I have also tried with and without an extra ‘.’ at the end of the domain, but still doesn’t verify. Plusnet shows the settings as
Left Field: (Blank)
Type: MX
Priority: 99
Right Field:ms52973062.msv1.invalid
Any help appreciated!
Nick


 
paris
Jan 30, 2012 at 1:31 pm

Don’t worry about the @ , the value should just be ms52973062.msv1.invalid with Priority 99. DNS does take a bit of time to update , I would use http://www.mxtoolbox.com/ to check the update has been applied


 

Reply

Copyright © 2012 Welcome to Pariswells.com All rights reserved. Theme by Laptop Geek.