By: jdnz
13 Apr 22:14

try over-riding your ISPs DNS ( use google DNS – 8.8.8.8 ) – my bet is your ISP has a caching resolver and it’s got stale data ( had that myself a few times with my ISP here in NZ )

you can use nslookup on your system to verify if it’s the cause – at the nslookup prompt just type ‘www.xferrecords.com‘ ( which will resolve using your ISP default dns ) , then type ‘server 8.8.8.8’ to just switch nslookup to using google and then ‘www.xferrecords.com‘ a 2nd time and see if you get a different resp…

Go to this post

Go to first unread post in this topic

Read more here: Source link

By: jdnz
13 Apr 22:14

try over-riding your ISPs DNS ( use google DNS – 8.8.8.8 ) – my bet is your ISP has a caching resolver and it’s got stale data ( had that myself a few times with my ISP here in NZ )

you can use nslookup on your system to verify if it’s the cause – at the nslookup prompt just type ‘www.xferrecords.com‘ ( which will resolve using your ISP default dns ) , then type ‘server 8.8.8.8’ to just switch nslookup to using google and then ‘www.xferrecords.com‘ a 2nd time and see if you get a different resp…

Go to this post

Go to first unread post in this topic

Read more here: Source link

By: jdnz
13 Apr 22:14

try over-riding your ISPs DNS ( use google DNS – 8.8.8.8 ) – my bet is your ISP has a caching resolver and it’s got stale data ( had that myself a few times with my ISP here in NZ )

you can use nslookup on your system to verify if it’s the cause – at the nslookup prompt just type ‘www.xferrecords.com‘ ( which will resolve using your ISP default dns ) , then type ‘server 8.8.8.8’ to just switch nslookup to using google and then ‘www.xferrecords.com‘ a 2nd time and see if you get a different resp…

Go to this post

Go to first unread post in this topic

Read more here: Source link