Domain Forwarding

91 Aufrufe Markdown

Send visitors from a registered domain to another address and change or remove that redirect from the same tab, so a parked or renamed domain starts earning traffic without anyone opening the provider's own control panel.

Opening the Screen

Open a domain from Orders › Services, then pick the Domain Forwarding tab: {admin}/services/detail?id={service}&content=domain-forwarding.

The tab is rendered only when two conditions hold together. The service type must be a domain, and the registrar module bound to that domain must expose a method for reading the current forwarding (get_forwarding or getForwardingDomain). A domain sold through a module without forwarding support has no tab at all, so you never meet an empty Domain Forwarding tab: either it is there and it works, or it is not there.

Service status is not part of that condition. Unlike Transfer, which is only added while the service is active, this tab stays available on a suspended or expired domain for as long as the module answers. That matters when you are winding a domain down: the redirect can still be removed after the service has been suspended.

Everything on this tab is executed at the registrar. WISECP keeps no local copy of the redirect, so the tab shows what the provider reports at the moment it is opened, not a value stored in this system.

What Is on the Screen

The tab holds a single card titled Domain Forwarding. The body of that card is not part of the page your browser received: it is fetched from the registrar the first time the tab is opened. A spinner sits in the middle of the card while that request is running, and it is replaced by one of two states.

Information line A standing blue note at the top of the card. It is always printed, in both states, and explains what domain forwarding does. It also mentions a frame-based (URL masking) redirect; that option is not offered on this screen, where only 301 and 302 exist, so there is nothing to look for in the window.
Forwarding status The live answer from the registrar: either one active redirect, or an empty state saying nothing is configured.
Action buttons They follow the state. An active redirect offers edit and cancel, an empty state offers a single button that opens the same window.

How and when the card loads

The request is sent once per page visit, the first time the tab becomes visible. If you reach the page through the address above, the tab is already active and the request starts with the page. If you open it by clicking the tab, it starts at that moment.

After that, the card is refreshed automatically at exactly two points: after a forward is set and after a forward is cancelled. Nothing else refreshes it. If someone changes the redirect directly at the registrar while your page is open, reload the page to see the new value.

A domain that is already forwarded

An active redirect is drawn as a single row that reads left to right: the forwarded domain, an arrow, and the destination written as a complete address with its protocol. A badge on the right of that row names the redirect type, either 301 Permanent or 302 Temporary.

Two icon buttons close the row. The pencil carries the tooltip Edit and opens the forwarding window filled with the current values. The cross carries the tooltip Cancel Forwarding and starts the removal described below.

A domain with no forwarding

When the registrar reports that nothing is configured, the card body becomes an empty state: an arrow icon, one sentence saying no forwarding is set up, and a green Set Forwarding button in the middle. That button is the only way into the window from this state.

The forwarding window

Both Set Forwarding and Edit open the same window with the same three controls. Only the title and the confirming button change: creating a redirect gives the title Set Domain Forwarding and the button Set Forwarding, while editing gives Edit Domain Forwarding and the button Save Changes.

The confirming button starts disabled and stays disabled while the destination is empty. When you are editing an existing redirect it also stays disabled until at least one of the three values differs from what was loaded, so re-saving an unchanged redirect is not possible by accident.

Fields

Destination URL Required, and marked with a red asterisk. The address visitors will land on, written without a protocol (the placeholder shows the expected shape). If you type or paste a complete address that begins with a protocol, that prefix is removed from the box and applied to the Protocol control instead, so the two never contradict each other. An empty value is refused by the server as well as by the disabled button.
Protocol Two choices, HTTP and HTTPS. A new redirect opens on HTTPS; editing an existing one shows the stored value. This is the protocol of the destination, not of the forwarded domain, so it has to match what the target site actually serves. Any value other than the two offered is stored as HTTP.
Redirect Type Two choices, 301 Permanent and 302 Temporary; the frame-based masking named in the note above the card is not one of them. A new redirect opens on 301 Permanent. Permanent tells browsers and search engines that the move is final and lets them cache it, which is what a renamed brand wants; temporary keeps the original address authoritative and is the safer choice for a campaign or a maintenance detour. Any value other than the two offered is stored as 301 Permanent.

Tasks

Setting up a forward

  1. Open the domain from Orders › Services and click the Domain Forwarding tab. Wait for the spinner to be replaced by the card body.
  2. Click the green Set Forwarding button in the middle of the empty state.
  3. In the Set Domain Forwarding window fill in Destination URL, then review Protocol and Redirect Type. The button at the bottom becomes clickable as soon as the destination is not empty.
  4. Click Set Forwarding at the bottom of the window. A short confirmation appears, the window closes, and the card reloads and now shows the active row with its destination and type badge. The redirect is live at the registrar from that moment; the change is also written to the operator's action log.

Changing an existing forward

  1. On the active row, click the pencil-shaped Edit button on the right.
  2. The Edit Domain Forwarding window opens with the current destination, protocol and type already filled in. Change what you need; the bottom button stays disabled until at least one value differs.
  3. Click Save Changes at the bottom of the window. The window closes and the card reloads with the new values.
  4. Read the row before you leave: it is drawn from a fresh answer by the registrar, so it is your confirmation that the provider accepted the change and not just that the request was sent.

Cancelling a forward

  1. On the active row, click the cross-shaped Cancel Forwarding button on the right.
  2. A confirmation window opens naming the domain and warning that visitors will no longer be redirected.
  3. Click Cancel Forwarding in that window. It closes, the card reloads, and the empty state returns.
  4. From that point the domain answers on its own again, which usually means whatever its nameservers point at. Cancelling removes the redirect at the registrar; it does not restore any earlier redirect.

Things to Watch

Every button here writes at the registrar

Setting, editing and cancelling are sent to the provider the moment you confirm, and WISECP stores no copy of the previous value. There is no undo on this tab: to go back you have to set the old destination again by hand, so note it before you change it.

An unreadable answer looks like an empty one

If the registrar refuses the read (expired credentials, provider outage, a domain the account no longer holds), the card falls back to the same empty state as a domain with no redirect. Before you conclude that nothing is forwarded, confirm the module is answering elsewhere on the page or check the module log.

Reading and writing are separate module abilities

The tab appears when the module can read a forward. Writing is a different method: a module that only reads shows the tab and the buttons but answers "Module does not support domain forwarding" when you confirm. Test one domain per registrar before promising the feature to customers.

Required Privileges

Reading the tab needs SERVICES_LOOK or SERVICES_OPERATION. Setting, editing and cancelling a forward all need SERVICES_OPERATION; a staff member with only the read privilege sees the buttons but the request is refused.

War das hilfreich?

Vielen Dank für Ihre Rückmeldung!

Brauchen Sie weitere Hilfe?

Unser Support-Team ist rund um die Uhr für Sie da, wenn Sie oben nicht fündig werden.

Kontakt aufnehmen Ticket eröffnen

Wir verwenden Cookies, um Sie angemeldet zu halten, Ihre Sprache und Währung zu merken und die Website zu verbessern. Cookie-Richtlinie