SSl still not being issued

#7

In this case it would appear as if you are not resolving your domain to Cloudflare. Try flushing any DNS related caches.

What does the following return?

ping sulavrajkolakshyapati.com.np
nslookup sulavrajkolakshyapati.com.np
ping www.sulavrajkolakshyapati.com.np
nslookup www.sulavrajkolakshyapati.com.np
0 Likes
#8

Deleted the screenshot

0 Likes
#9

All right, you can delete the screenshot now if you dont want the IP address public.

Your domain does not resolve to the right address at Cloudflare. That is most likely a propagation issue. Do you have any way to flush your DNS cache? Otherwise you would need to wait until it updates. Alternatively you can switch to another public DNS resolver.

0 Likes
#10

how to flush DNS cache? how to switch to another DNS resolver?

0 Likes
#11

Try rebooting your router or whatever runs on your .254 address

https://dns.yandex.com/ or https://cloudflare-dns.com/

0 Likes
#12

I restarted router and switched to another dns. But still not working…

0 Likes
#13

Switching DNS should definitely have fixed it. Can you post once more the output of

ping sulavrajkolakshyapati.com.np
nslookup sulavrajkolakshyapati.com.np
ping www.sulavrajkolakshyapati.com.np
nslookup www.sulavrajkolakshyapati.com.np
0 Likes
#14

plz look

Untitled1
Untitled1.png1366×768 73.5 KB

1 Like
#15

Now that is interesting. You do seem to resolve against Cloudflare but still get the server IP.

Can you also run the following?

nslookup sulavrajkolakshyapati.com.np 1.1.1.1
nslookup sulavrajkolakshyapati.com.np 1.0.0.1
nslookup sulavrajkolakshyapati.com.np 77.88.8.8
nslookup sulavrajkolakshyapati.com.np 77.88.8.1
nslookup sulavrajkolakshyapati.com.np 8.8.8.8
nslookup sulavrajkolakshyapati.com.np 8.8.4.4

nslookup www.sulavrajkolakshyapati.com.np 1.1.1.1
nslookup www.sulavrajkolakshyapati.com.np 1.0.0.1
nslookup www.sulavrajkolakshyapati.com.np 77.88.8.8
nslookup www.sulavrajkolakshyapati.com.np 77.88.8.1
nslookup www.sulavrajkolakshyapati.com.np 8.8.8.8
nslookup www.sulavrajkolakshyapati.com.np 8.8.4.4
0 Likes
#16

Still doesnt work/…

Untitled2
Untitled2.png1366×768 73.7 KB
Untitled3
Untitled3.png1366×768 65.4 KB
Untitled4
Untitled4.png1366×768 70.7 KB
Untitled5
Untitled5.png1366×768 60.8 KB

0 Likes
#17

It appears as if all nameservers do point to that CNAME which points to your server instead of pointing to Cloudflare. I am afraid I do not have a reasonable explanation for that at the moment.

http://sitemeer.com/#www.sulavrajkolakshyapati.com.np, for example, should show you that it domain actually resolves to Cloudflare.

What does nslookup -type=ns sulavrajkolakshyapati.com.np 1.1.1.1 return?

0 Likes
#18

The only possibly remotely reasonable explanation could be that there is some error with your DNS setup. http://dnsviz.net/d/sulavrajkolakshyapati.com.np/dnssec/ shows several errors in this area.

0 Likes
#19

Returns this

sulavrajkolakshyapati.com.np nameserver = bella.ns.cloudflare.com
sulavrajkolakshyapati.com.np nameserver = rick.ns.cloudflare.com

0 Likes
#20

Returns the right nameservers. I am afraid I cant tell why the wrong values are returned.

Can you post the link https://cloudflare-dns.com/help gives you?

0 Likes
#21

image
image.png657×815 26.4 KB

0 Likes
#22

Can you also post the link?

0 Likes
#23
0 Likes
#24

Your setup looks fine. I am afraid I do not have an explanation why the KTM PoP would resolve to the CNAME instead of the configured record.

Contact Cloudflare support at https://support.cloudflare.com/requests/new

Also, tagging @cloonan, @cscharff, and @mnordhoff

0 Likes
#25

anyways thanks for the support sandro. now it has worked.:smiley:

0 Likes
closed #26

This topic was automatically closed after 30 days. New replies are no longer allowed.

0 Likes