37 ms·

Hi, thanks. None of those 3 sites open here. What kind of information do you need from ipleak.net? DNS Address - 1 server 45.62.204.178 Canada Canada

by vit05 9y ago

CydeWeys 9y ago
What browser are you using? It does seem like you're having DNS problems. See the following: $ dig @45.62.204.178 blog.google ; <<>> DiG 9.9.5-3ubuntu0.16-Ubuntu <<>> @45.62.204.178 blog.google ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached That same command run against other DNS servers (for example, our public DNS server at 8.8.8.8) succeeds. Even stranger, against your configured DNS server, requests for non-existent .google domains do work correctly, as does nic.google and sites on many of the rest of our TLDs (e.g. get.how and iam.soy). nic.dev and bar.foo do work for me but pki.goog and nomulus.foo do not. It looks to me like you're having DNS problems. Can you switch your DNS settings? Or use a VPN that does that built-in? Also, why, if you're in Brasil, are you hitting a DNS server located in Canada?
- vit05 9y ago
  I have changed the DNS and now it is working correctly. Two days ago, a problem occurred with the modem and they changed the device. All settings were on automatic. But I really can not understand why blog.google did not work right away, and why it was routed to a canada DNS. I am using Google Chrome and Firefox. Tks for take the time to help. The internet provider that I am using is called netcombo.com.br and in the past, they have blocked the use of others DNS and some services. I do not know if that is the case now. I have asked for others using the same internet provider to test and will update when they done. Edit. So, others using the same provider reporter that https://www.blog.google https://www.blog.google do not open there.
  - CydeWeys 9y ago
    Thanks for your debugging help. I'm working to see what the next step might be to contact people at that ISP and tell them that they're messing something up. You could also tell them via their tech support that they're misrouting requests for certain TLDs.

Hi, thanks. None of those 3 sites open here. What kind of information do you need from ipleak.net? DNS Address - 1 server 45.62.204.178 Canada Canada

by vit05 9y ago

Hi, thanks. None of those 3 sites open here. What kind of information do you need from ipleak.net? DNS Address - 1 server 45.62.204.178 Canada Canada

CydeWeys 9y ago

What browser are you using? It does seem like you're having DNS problems. See the following: $ dig @45.62.204.178 blog.google ; <<>> DiG 9.9.5-3ubuntu0.16-Ubuntu <<>> @45.62.204.178 blog.google ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached That same command run against other DNS servers (for example, our public DNS server at 8.8.8.8) succeeds. Even stranger, against your configured DNS server, requests for non-existent .google domains do work correctly, as does nic.google and sites on many of the rest of our TLDs (e.g. get.how and iam.soy). nic.dev and bar.foo do work for me but pki.goog and nomulus.foo do not. It looks to me like you're having DNS problems. Can you switch your DNS settings? Or use a VPN that does that built-in? Also, why, if you're in Brasil, are you hitting a DNS server located in Canada?

vit05 9y ago
I have changed the DNS and now it is working correctly. Two days ago, a problem occurred with the modem and they changed the device. All settings were on automatic. But I really can not understand why blog.google did not work right away, and why it was routed to a canada DNS. I am using Google Chrome and Firefox. Tks for take the time to help. The internet provider that I am using is called netcombo.com.br and in the past, they have blocked the use of others DNS and some services. I do not know if that is the case now. I have asked for others using the same internet provider to test and will update when they done. Edit. So, others using the same provider reporter that https://www.blog.google https://www.blog.google do not open there.
- CydeWeys 9y ago
  Thanks for your debugging help. I'm working to see what the next step might be to contact people at that ISP and tell them that they're messing something up. You could also tell them via their tech support that they're misrouting requests for certain TLDs.