UltraDNS Web Forwarding Guide

This guide provides frequently asked questions, common use cases, and common issues related to UltraDNS Web Forwarding.

Frequently Asked Questions

• What are the differences between Framed, 301 and 302 Redirects for UltraDNS Web Forwarding? 
• Do You Support Cloaked Web Forwards? 
  Yes. This is what we refer to as framed web forwards.
• How do you use wildcards in Web Forwarding records? 
  Information on where wildcards can be used and how they behave.
• Can Web Forwarding use HTTPS? 
  Supports HTTPS to HTTPS, HTTPS to HTTP, HTTP to HTTP, and HTTP to HTTPS.
• Why do I have records that point to crs.ultradns.net, 204.74.99.100 or 204.74.99.200? 
  Explains why those resource records are required for web forwarding.
• Why do Web Forwarding records have 300-second TTLs? 
  Explains why the TTL is set to this value and why it cannot be edited.
• Where are the Web Forwarding and Mail Forwarding servers located? 
  Lists the locations of the Web Forwarding infrastructure.

Common Use Cases

• Web Forwarding: How do I forward all pages from a host to a particular webpage? 
  Use this process to redirect all pages to a single landing page.
• Web Forwarding: How do I map pages from one host to matching pages on another host? 
  Use this process to forward pages while preserving URL structure.

Common Issues

• Error: "Resource Record with these attributes already exists. Cannot add Web Forward for this URL." when Creating Web Forwarding Record in UI 
  Occurs when conflicting A or CNAME records already exist.
• URL isn’t being masked by web forward 
  Applies when a framed or cloaked forward still shows the redirect URL.
• Blank Page after Creating Web Forwarding Record