Posted by WCS on

We have an existing website/Domain name - whitbycivicsociety.org.uk with the current IPS TAG of 123-REG. You have approved our request for an eVoice website and we are currently happy with it and now want to implement it. One of our members has contacted 123-REG and asked what they need to allow us to implement our new site. They have asked us to let them know what your IPS TAG is, so could you please let me know ?

In order to implement our new website under the existing Domain name is that all under the control of 123-REG or do we have to do something from our end too? for example do I need to add whitbycivicsociety.org.uk in the box in section ADD DOMAIN NAME under EXTERNAL DOMAIN OPTIONS under WEBSITE SETTINGS ?

Thank you in advance.

Peter Craggs (Whitby Civic Society)

Posted by Voice Admin on

You don't want to change the IPS Tag - we don't host the domain itself, just the website.

You would need the IPS Tag to move the domain from 123-Reg to another registrar.

Instead, just go to the DNS settings for your site within the 123-Reg control panel, and set up an A record for www.whitbycivicsociety.org.uk pointing to the e-voice server at 46.20.114.134.

There are some instructions for domain names in the documentation, including some 123-reg specific bits.

Thanks

Joe - Voice Admin

Posted by Deleted User on

Joe, we would like to migrate from old web site and make a new one but cant get admin access to our web site any more due to staff changes. How do we get the Chair of Council to be an administrator without having such access?

OR we are happy to keep current web site so long as we can decide who is admin and who is not.

Thanks, Barry

Posted by Voice Admin on

I can add you as an admin of the existing site, and then you can manage who does/doesn't have admin access. A site can have as many or as few administrators as you like.

Probably best if you send me an email at admin@e-voice.org.uk confirming which account you would like to be the admin, and for which site. (rather than adding the details here on the forum!)

Thanks

Joe

Posted by Hett Village Hall on

Hi,  we are having the same issue, can I also use 46.20.114.134 with my domain provider?  As they are asking for our IPS tag also

Thanks 

 

Posted by Joe Oldak on

Firstly to clarify a few of things:

  • Domain names are bought and managed via a registrar - like 123-reg or GoDaddy etc (there are lots - too many to list here!).
  • You manage the DNS from the registrar's control panel.
  • You can use this to create a DNS record pointing to e-voice's IP address - which is 83.136.248.56 (not 46.20....)

Importantly, e-voice is NOT a registrar. You can't register domains or manage your DNS from e-voice.

e-voice is just a website provider, and doesn't care which registrar you use for your domain. Use whichever is cheapest or most convenient, and just set the DNS records for your e-voice website.

The only reason anyone needs an IPS tag is to move your domain between registrars.

The only reason you would want to do this is if a different registrar is considerably "better" than the one you're currently using - e.g., they're cheaper or have an easier to use control panel or whatever - pick your own definition of "better"!

So, with that in mind...

From an e-voice perspective, there's no reason for you to need an IPS tag to set up your domain to work with your e-voice website. All you need to do is update the DNS records.

HOWEVER - if your existing hostname provider doesn't allow you to set custom DNS records, then you could switch to a different registrar in order to gain this feature. That would mean switching to 123-reg or GoDaddy or the registrar of your choice, and then once switched you'd use the DNS settings from their control panel to point the domain to e-voice.

I hope that helps?

Cheers

Joe

 

Posted by Hett Village Hall on

Hi Joe,

I have migrated the domain across and it is now saying that the website is not secure?  What do i need to do to solve this?

thanks

Victoria

Posted by Joe Oldak on

The problem is that there's an AAAA record in the DNS pointing to the wrong place, as well as the correct A record.

Delete the AAAA record, then wait a while, and the certificate should be automaticaly created.

Thanks

Joe