DNS only but the working mode is proxy

Since last night, all my DNS records suddenly show DNS only when I check them, but they are actually running in proxy mode. As a result, my site cannot be opened.
I tried to re-create the dns only record, but the result was the same

What’s the domain and post a screenshot of your DNS entries.

curl -v https://kr2.898978.xyz/

  • Trying 146.56.46.16:443…
  • Connected to kr2.898978.xyz (146.56.46.16) port 443 (#0)
  • ALPN: offers h2,http/1.1
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • CAfile: /etc/ssl/certs/ca-certificates.crt
  • CApath: /etc/ssl/certs
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
  • ALPN: server accepted http/1.1
  • Server certificate:
  • subject: CN=*.898978.xyz
  • start date: May 29 23:34:34 2024 GMT
  • expire date: Aug 27 23:34:33 2024 GMT
  • subjectAltName: host “kr2.898978.xyz” matched cert’s “*.898978.xyz”
  • issuer: C=US; O=Let’s Encrypt; CN=R3
  • SSL certificate verify ok.
  • using HTTP/1.1

GET / HTTP/1.1
Host: kr2.898978.xyz
User-Agent: curl/7.88.1
Accept: /

< HTTP/1.1 301 Moved Permanently
< Date: Thu, 13 Jun 2024 06:58:12 GMT
< Content-Type: text/html
< Content-Length: 167
< Connection: keep-alive
< Cache-Control: max-age=3600
< Expires: Thu, 13 Jun 2024 07:58:12 GMT
< Location: https://kr2.898978.xyz/
< Report-To: {“endpoints”:[{“url”:“https://a.nel.cloudflare.com/report/v4?s=0Dnj8IBqo66p5NYNvkpNi0apqs8wPhPcHMdLw0cECOtUqPd3hRZnjDA%2FWm3z%2FB%2F8RUgOgjMDi6aQ3F3hHH4D27kOIfwwqb4Wvi%2FPPDfMmdFE2w2MOztrATCKQj1IoyINRw%3D%3D”}],“group”:“cf-nel”,“max_age”:604800}
< NEL: {“success_fraction”:0,“report_to”:“cf-nel”,“max_age”:604800}
< Server: cloudflare
< CF-RAY: 893030db3d5730fd-ICN
< alt-svc: h3=“:443”; ma=86400
<

301 Moved Permanently

301 Moved Permanently


cloudflare * Connection #0 to host kr2.898978.xyz left intact

Connected to kr2.898978.xyz (146.56.46.16) port 443 (#0) The connection is to my server, but I can see the response from cloudflare. This is amazing

curl -v https://kr2.898978.xyz/

  • Trying 146.56.46.16:443…
  • Connected to kr2.898978.xyz (146.56.46.16) port 443 (#0)
  • ALPN: offers h2,http/1.1
  • TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • CAfile: /etc/ssl/certs/ca-certificates.crt
  • CApath: /etc/ssl/certs
  • TLSv1.3 (IN), TLS handshake, Server hello (2):
  • TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
  • TLSv1.3 (IN), TLS handshake, Certificate (11):
  • TLSv1.3 (IN), TLS handshake, CERT verify (15):
  • TLSv1.3 (IN), TLS handshake, Finished (20):
  • TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
  • TLSv1.3 (OUT), TLS handshake, Finished (20):
  • SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
  • ALPN: server accepted http/1.1
  • Server certificate:
  • subject: CN=*.898978.xyz
  • start date: May 29 23:34:34 2024 GMT
  • expire date: Aug 27 23:34:33 2024 GMT
  • subjectAltName: host “kr2.898978.xyz” matched cert’s “*.898978.xyz”
  • issuer: C=US; O=Let’s Encrypt; CN=R3
  • SSL certificate verify ok.
  • using HTTP/1.1

GET / HTTP/1.1
Host: kr2.898978.xyz
User-Agent: curl/7.88.1
Accept: /

< HTTP/1.1 301 Moved Permanently
< Date: Thu, 13 Jun 2024 06:58:12 GMT
< Content-Type: text/html
< Content-Length: 167
< Connection: keep-alive
< Cache-Control: max-age=3600
< Expires: Thu, 13 Jun 2024 07:58:12 GMT
< Location: https://kr2.898978.xyz/
< Report-To: {“endpoints”:[{“url”:“https://a.nel.cloudflare.com/report/v4?s=0Dnj8IBqo66p5NYNvkpNi0apqs8wPhPcHMdLw0cECOtUqPd3hRZnjDA%2FWm3z%2FB%2F8RUgOgjMDi6aQ3F3hHH4D27kOIfwwqb4Wvi%2FPPDfMmdFE2w2MOztrATCKQj1IoyINRw%3D%3D”}],“group”:“cf-nel”,“max_age”:604800}
< NEL: {“success_fraction”:0,“report_to”:“cf-nel”,“max_age”:604800}
< Server: cloudflare
< CF-RAY: 893030db3d5730fd-ICN
< alt-svc: h3=“:443”; ma=86400
<

301 Moved Permanently

301 Moved Permanently


cloudflare * Connection #0 to host kr2.898978.xyz left intact
  • Connected to kr2.898978.xyz (146.56.46.16) port 443 (#0)
    The connection is to my server, but I can see the response from cloudflare. This is amazing

Resolves just fine to the server, as evident also by your screenshot.

But my server does not return the “HTTP/1.1 301 Moved Permanently” logic.
“Server: cloudflare ”
From this content, we can see that cloudflare returned the content. But my IP is my own server. How did cloudflare modify the result returned by my actual server?

It seemingly does because the connection goes straight to your server.

Your server then seems to involve Cloudflare somehow, but that’s something you need to check on the server.

DNS only cloudflare servers should not be involved in my response。

If your server forwards a Cloudflare response, it will certainly show that.

The point is, the DNS resolution works as expected. What your server then does, is something you have to clarify with your host I am afraid.

It was working fine until last night without any changes.

As mentioned, only your host can help you here.

Thank you for your reply, I will continue to analyze it.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.