Issue with DNS Resolution and Unexpected Redirects/Error 1000
Hi Cloudflare Community,
I’m experiencing an issue with DNS resolution and unexpected behavior across two zones in my Cloudflare account. Here’s the setup and the problem:
Setup
Zone 1: example.com (Partial setup, enterprise account)
For foo.example.net and foo.example2.net to resolve to the same origin IP as foo.example.com.
Actual Behavior
Why is foo.example.net redirecting to www.example.net despite no configured redirect rules?
Why is foo.example2.net returning an Error 1000?
How can I configure these records to resolve to the correct origin IP without issues?
Any insights or suggestions would be greatly appreciated!
Thank you!
I’m experiencing an issue with DNS resolution and unexpected behavior across two zones in my Cloudflare account. Here’s the setup and the problem:
Setup
Zone 1: example.com (Partial setup, enterprise account)
- A Records:
foo.example.com pointing to an origin IP (proxied).
www.example.com pointing to an origin IP (proxied). - CNAME Records at Authoritative DNS Provider (Not a Cloudflare):
foo.example.com -> www.example.com.cdn.cloudflare.net
www.example.com -> www.example.com.cdn.cloudflare.net
- CNAME Record:
foo.example.net -> foo.example.com (proxied).
- CNAME Record:
foo.example2.net -> foo.example.com (proxied).
For foo.example.net and foo.example2.net to resolve to the same origin IP as foo.example.com.
Actual Behavior
- When accessing foo.example.net, I receive a 301 redirect to www.example.net. There are no redirect or page rules set up that would cause this behavior.
- When accessing foo.example2.net, I receive the following error:
Error 1000: DNS points to prohibited IP...
Why is foo.example.net redirecting to www.example.net despite no configured redirect rules?
Why is foo.example2.net returning an Error 1000?
How can I configure these records to resolve to the correct origin IP without issues?
Any insights or suggestions would be greatly appreciated!
Thank you!
