URL forwarding -- Error Processing Request

qiqihar

New Member
today system url forwarding been error, as following:

Error Processing Request
The domain you are attempting to access uses URL forwarding provided by easyDNS
An error has occurred and we cannot URL forward this request. This may be a temporary error. Please try again later.


please fix it soon!
 

sandy

Administrator
Staff member
please reply with the domain name of concern and I will see what I can do

thanks
sandy
 

sandy

Administrator
Staff member
HI there

you cannot use STEALTH forwarding to forward to a HTTPS site. Please change then to be regular URL forwards and let me know when complete so I can make sure they load properly

thanks
sandy
 

sandy

Administrator
Staff member
for Qiqihar

can you pleas add a test URL forward on your domain.. as you have removed the URL forwards i cannot investigate the zone problem

thanks
sandy
 

yalnizadalar

New Member
As is the case for Michael; suddenly all started working now. I am curious what happened and/or changed in the mean time.

Anyhow, thanks to the support team.

Y
 

Herberti

New Member
Hallo!

What does not work ANYMORE is using "https" for URL-forwardings.

https:// test.guetlbauer.com

worked till last week. Now I get

Vorübergehender DNS-Fehler. Versuchen Sie, die Seite zu aktualisieren.
Fehlercode: INET_E_RESOURCE_NOT_FOUND

(Temporary DNS-error. Try again later.)

Any idea?

Michael
 

Herberti

New Member
URL above (test.guetlbauer.com ) is separated from protocol prefex (https://) because your forum system says otherwise, it's not allowed (spam or so ...)
 
Last edited:

sandy

Administrator
Staff member
test2.guetlbauer.com
will forward to and resolve at the HTTPS being forwarded to site but you would not be able to visit https://test2.guetlbauer.com
without a certificate for
test2.guetlbauer.com
or a wildcard certificate for
guetlbauer.com
 

Herberti

New Member
I see. I thought, it worked in the past, but as you wrote, it can't have been working ever, right?

Is there any way, to prevent a pointless error page but at least getting a certificate error and then doing the forward?

Michael
 

sandy

Administrator
Staff member
the error was an issue on the side of our web forwarding server.. which has now been repaired.

thanks..
 

sandy

Administrator
Staff member
how to??? can you please be more specific and include the domain name of concern

thanks
 

sandy

Administrator
Staff member
sorry I would need more information what is the domain name and please be more specific when you say device,

thanks
 

Herberti

New Member
Hallo again! Is there again a problem with your web forwarding server?

Requests to test.guetlbauer.com --> www.orf.at sometimes (!) work, more often the browser stucks and ends with "ERR_NETWORK_CHANGED".

(BTW, is there no monitoring of your servers? Even after the last glitch this should have been implemented - PLEASE!)

Michael
 

sandy

Administrator
Staff member
what does the record actually look like at buddy dns?

dig @b.ns.buddyns.com a test.guetlbauer.com

; <<>> DiG 9.10.6 <<>> @b.ns.buddyns.com a test.guetlbauer.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62792
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;test.guetlbauer.com. IN A

;; ANSWER SECTION:
test.guetlbauer.com. 300 IN CNAME url-fwd.zoneedit.com.

;; Query time: 55 msec

_____________________________

what is the actual record?

regards.
 

Herberti

New Member
Which information do you need?

There seems to be a problem with data transfer from zoneedit.

First I got this result:

1665580355451.png

And after a new sync this:

1665580723727.png

Michael

 

Herberti

New Member
BTW, it seems ZONEEDIT still lists outdated buddyns server:

Zone/Registry consistentERRORThe list of nameservers declared by the last delegating server and the authoritative server do not match. This occasionally entails important issues. Configuration should be reviewed ASAP. Entries which differ are:
  • b.ns.buddyns.com
  • c.ns.buddyns.com
  • uz5154v9zl2nswf05td8yzgtd0jl6mvvjp98ut07ln0ydp2bqh1skn.free.ns.buddyns.com
  • uz53c7fwlc89h7jrbxcsnxfwjw8k6jtg56l4yvhm6p2xf496c0xl40.free.ns.buddyns.com
  • uz5x36jqv06q5yulzwcblfzcrk1b479xdttdm1nrgfglzs57bmctl8.free.ns.buddyns.com

As I understand the instuctions here


there should be no "b.ns..." or "c.ns...", should it?

Michael
 
Top