I set my domain name servers SCREENPLAY.MOBI on 3/2/2017 but still didn't reached us actually it propagate to only few (5) servers around the world in Europe.
The odd thing it start propagate from India!!
I double checked the name servers they are correct
I contacted Godaddy and bluehost(host provider) with no luck
Today is the fifth day and no changes at all!!
Solved! Go to Solution.
That does sound odd as the longest (most extreme) cases of domain propagation is 48 hours. You mentioned that it propagated in some regions but in your area there's been no change for over 5 days? This sounds more like a caching issue.
Have you tried clearing your local cache settings on your browser or even accessing from another device or network if possible?
I don't have to do that as bluehost don't see it too
The Godaddy support said that it can take more than 4 days!!!
You can try or anybody
I don't believe this is a DNS propagation issue. I've ran a few public tests through Pingdom tools, HostTracker, and a DNS DiG lookup. The first two are hitting the nameservers at ns1/ns2 bluehost.com, but they're also coming up with "Host not found" results. When reviewing further in DiG, there doesn't appear to be any A zone records pointing to an IP address for your site.
If Bluehost is the hosting provider, I would reach out to them once more to verify that you're using the correct authoritative nameservers or have them correct the zone records for you to have your domain pointed to your hosted site.
We can push it on our end for once the name servers actually point to us but until godaddy pushes the nameservers again so it'll propagate everywhere, our records won't take effect.
Please advise Bluehost that the domain is already pointing to NS1/NS2 nameservers. I've just ran another public DiG test with trace results to confirm this at Kloth.net which returned the following:
; <<>> DiG 9 <<>> @localhost screenplay.mobi A ; (1 server found) ;; global options: +cmd . 257667 IN NS d.root-servers.net. . 257667 IN NS c.root-servers.net. . 257667 IN NS a.root-servers.net. . 257667 IN NS l.root-servers.net. . 257667 IN NS i.root-servers.net. . 257667 IN NS f.root-servers.net. . 257667 IN NS k.root-servers.net. . 257667 IN NS j.root-servers.net. . 257667 IN NS g.root-servers.net. . 257667 IN NS m.root-servers.net. . 257667 IN NS e.root-servers.net. . 257667 IN NS b.root-servers.net. . 257667 IN NS h.root-servers.net. . 265899 IN RRSIG NS 8 0 518400 20170318170000 ( 20170305160000 61045 . Hq7I/GdHakgCrQo9UdXhMKl62m/Bi4awe6uemH22y9BT BdBqNqNjet0sEYo38uJ84mcIdWInZhCCIYPNEDe3aTKu ajuNOmSOOQj/0PjurTcLB7vxHy/fitOBqE4Lck5Xun+A tZA8Xwl+qkyInMjNYTQfKxH4ITgMk13E7G59Qs7QKLHS aH+uEjC2MZm6ueEwJnGSQxUYtBkDUtipEDYs5y9hvBnc EGYWgNOCy/8Fpq8UPn4i68NjMLhKp4wi/f+1FeV2h1h/ EuFp0f0b5iMcTyHvl23xKacifeVuFi+h121bHgR6EQNU 4xBeqIS0ASi8aZ1gRaeKH0qirn2W/QOuWg== ) ;; Received 525 bytes from 127.0.0.1#53(127.0.0.1) in 3 ms mobi. 172800 IN NS a0.mobi.afilias-nst.info. mobi. 172800 IN NS b2.mobi.afilias-nst.org. mobi. 172800 IN NS c0.mobi.afilias-nst.info. mobi. 172800 IN NS d0.mobi.afilias-nst.org. mobi. 172800 IN NS a2.mobi.afilias-nst.info. mobi. 172800 IN NS b0.mobi.afilias-nst.org. mobi. 86400 IN NSEC mobile. NS RRSIG NSEC mobi. 86400 IN RRSIG NSEC 8 1 86400 20170321050000 ( 20170308040000 61045 . CIOKzVHFxemoAcHimmxpUx9oPy12intOiUO2DZ7r7eTH 9lh08v4t1x+frVUP41d7GjrQLG4eJ/JJGOfCtFaueV2K 0BJ+xADXF8qpJU8f6//LCC6g0fppv7nW2nXhGUBvRue9 5O2BsGTGszyJGgY8qNzjpdokNA9uJcCSHeoC4OJFt8R6 jNwclN/ErJSnXcoQgL8aueYyKz5ugtT3l/eALRDZKJ8v aYj3KDkzoGwlCHV0qveIkijpDNI2ScZAzGy1GBWvalvn geLUbA1jhwRaViV49Ql7oULURHaHmaQbL/oITgXXgDWZ Xi6C9xCaxnx/6hO4jcQo8ndIC4Ij+gphtw== ) ;; Received 766 bytes from 18.104.22.168#53(22.214.171.124) in 1128 ms screenplay.mobi. 86400 IN NS ns2.bluehost.com. screenplay.mobi. 86400 IN NS ns1.bluehost.com. 4jmu8d0v3g0t0e903ksv13lcfsq0pmba.mobi. 86400 IN NSEC3 1 1 1 D399EAAB 4LFBEHDR43T680U0Q4VKC3MGCD3NR7NS NS SOA RRSIG DNSKEY NSEC3PARAM 4jmu8d0v3g0t0e903ksv13lcfsq0pmba.mobi. 86400 IN RRSIG NSEC3 7 2 86400 20170329161127 ( 20170308151127 9072 mobi. N7IqvVQ+nzYCMRW0Jk+JaDOs/LGdTGpZWvScNZfaKrti MJsCueDbDmJs5K7JGpuzEMNcayZH6UBmQ7mUO4tiNy/F 1oEg+fJZ/d0plhtJKif2fMx7nlF1KrGYf3pCaOTVHqZ4 mbX3zlX0s0aXYn2IZv/xoZYtzBykX/NDTpfQVjA= ) tqrsdkb47t80mosgaa3mpd6l0c987clk.mobi. 86400 IN NSEC3 1 1 1 D399EAAB U1454A620JCKVC7Q5O3BSH04NKKAHGNH tqrsdkb47t80mosgaa3mpd6l0c987clk.mobi. 86400 IN RRSIG NSEC3 7 2 86400 20170322151746 ( 20170301141746 9072 mobi. F7pjeHBfrVKbRzOaKJhgibuD8fuOiwwRGK8p2heMLLC3 DOvjOeMxV3ElMOy3eoJVr36LyXZSfNVN5fpkOwu3cd2V azGhRbBF/xYFYfnyjBW9enB2FTlQyeTZ6Emota23rbiB MuEEzX2TiR7R3akmGBdytAiVoAfZDGKhWjYQaNM= ) ;; Received 579 bytes from 2001:500:22::1#53(2001:500:22::1) in 42 ms ;; Received 44 bytes from 126.96.36.199#53(188.8.131.52) in 5 ms
I've also ran this by our Domain team who pushed a reconcile event through earlier just to be sure. The domain is (as it has been for some time now) pointing to Bluehost. If NS1/NS2 are the not the correct nameservers then they need to verify which ones are so you can go in and point the domain name to the correct ones, otherwise they'll need to correct the missing DNS zone files.