dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
3278
share rss forum feed

rnijmeh

join:2012-07-20
Scarborough, ON
reply to Ian

Re: How to tell if Rogers blocks my URL?

said by Ian:

Doesn't resolve for me (Rogers DNS). Does if I use Google's public DNS.

Thanks for testing Ian! So what can I do to ensure Rogers DNS DOES resolve the site? Is there someone I can contact?


Ian
Premium
join:2002-06-18
ON
kudos:3
said by rnijmeh:

Thanks for testing Ian! So what can I do to ensure Rogers DNS DOES resolve the site? Is there someone I can contact?

I would contact the host provider. I'm not an expert, but saw this before with someone else that had a new site hosted. I'd bet that the provider didn't publish the DNS information properly. But can't be certain. In any case, they could at least re-do it. Might take a day or so to propagate.

You can test whether a particular DNS server is resolving that correctly with NSLOOKUP in the windows command prompt. As in this example. Change the DNS server as needed. In this example 8.8.8.8 is Google public DNS, 64.71.255.198 is dns.rnc.net.cable.rogers.com as set by rogers in my modem/wireless router. Adjust with the server command to test others as needed.



--
“Any claim that the root of a problem is simple should be treated the same as a claim that the root of a problem is Bigfoot. Simplicity and Bigfoot are found in the real world with about the same frequency.” – David Wong


yyzlhr

@rogers.com
reply to rnijmeh
How can it be a Rogers DNS problem if certain Rogers customers can access the site using the Rogers DNS. I have had no problem accessing the OP's site using the Rogers DNS, and a few others here have not reported problems either.


Ian
Premium
join:2002-06-18
ON
kudos:3
said by yyzlhr :

How can it be a Rogers DNS problem if certain Rogers customers can access the site using the Rogers DNS. I have had no problem accessing the OP's site using the Rogers DNS, and a few others here have not reported problems either.

Care to show which Rogers DNS server resolves the site correctly?
--
“Any claim that the root of a problem is simple should be treated the same as a claim that the root of a problem is Bigfoot. Simplicity and Bigfoot are found in the real world with about the same frequency.” – David Wong

rnijmeh

join:2012-07-20
Scarborough, ON
reply to Ian
Thanks for the tip, Ian! I'm sending this thread to my web host to see what they can do.


yyzlhr

@rogers.com
reply to Ian
said by Ian:

said by yyzlhr :

How can it be a Rogers DNS problem if certain Rogers customers can access the site using the Rogers DNS. I have had no problem accessing the OP's site using the Rogers DNS, and a few others here have not reported problems either.

Care to show which Rogers DNS server resolves the site correctly?

67.71.255.198


Ian
Premium
join:2002-06-18
ON
kudos:3

1 edit
said by yyzlhr :

said by Ian:

said by yyzlhr :

How can it be a Rogers DNS problem if certain Rogers customers can access the site using the Rogers DNS. I have had no problem accessing the OP's site using the Rogers DNS, and a few others here have not reported problems either.

Care to show which Rogers DNS server resolves the site correctly?

67.71.255.198

Think a number may be off...Sure that's not an IP address for something internal to you, like a modem?

> 67.71.255.198
Server:  [8.8.4.4]
Address:  8.8.4.4
 
*** [8.8.4.4] can't find 67.71.255.198: Non-existent domain
>
 

--
“Any claim that the root of a problem is simple should be treated the same as a claim that the root of a problem is Bigfoot. Simplicity and Bigfoot are found in the real world with about the same frequency.” – David Wong


yyzlhr

@rogers.com
Oops made a typo. First digit should be 64.


Ian
Premium
join:2002-06-18
ON
kudos:3
said by yyzlhr :

Oops made a typo. First digit should be 64.

Interesting. That's the same server I had tried before. Maybe the problem is intermittent and indeed internal to Rogers. Or it's been fixed.
--
“Any claim that the root of a problem is simple should be treated the same as a claim that the root of a problem is Bigfoot. Simplicity and Bigfoot are found in the real world with about the same frequency.” – David Wong


yyzlhr

@rogers.com
It's been working for me since this thread started.


Ian
Premium
join:2002-06-18
ON
kudos:3
said by yyzlhr :

It's been working for me since this thread started.

As I showed in my screen-shot, that same server timed-out rather than respond. And that was done seconds before I posted it. Again, probably an intermittent issue.
--
“Any claim that the root of a problem is simple should be treated the same as a claim that the root of a problem is Bigfoot. Simplicity and Bigfoot are found in the real world with about the same frequency.” – David Wong

arahman56

join:2011-08-11
Etobicoke, ON
reply to rnijmeh
Click for full size
Click for full size
Yep, something's off with Rogers's DNS server. BlockAid/OpenDNS resolves the server fine, but with Rogers, the request times out.

rnijmeh

join:2012-07-20
Scarborough, ON
reply to rnijmeh
Thanks for all your help!

Okay so here's an update... got an email from a very technically savvy customer who was trying to reach my site several times, but it wouldn't work reliably.

He figured out that my secondary DNS has no record for my site - so if the primary DNS fails, there's no fall back.

So I sent this info to my we host and they added the 2nd DNS... it's propagated (this was done 3 days ago), so it *should* be working now.

Could anyone who's on Rogers (who couldn't access before) test it out again to see if the site shows up now (finally!)?

Thanks for all your help everyone!


Ian
Premium
join:2002-06-18
ON
kudos:3
said by rnijmeh:

Could anyone who's on Rogers (who couldn't access before) test it out again to see if the site shows up now (finally!)?

Thanks for all your help everyone!

> server 8.8.4.4
Default Server: [8.8.4.4]
Address: 8.8.4.4

> plr.me
Server: [8.8.4.4]
Address: 8.8.4.4

Non-authoritative answer:
Name: plr.me
Address: 69.160.53.72

> server 64.71.255.198
Default Server: dns.rnc.net.cable.rogers.com
Address: 64.71.255.198

> plr.me
Server: dns.rnc.net.cable.rogers.com
Address: 64.71.255.198

Non-authoritative answer:
Name: plr.me
Address: 69.160.53.72

Seems to be working. Then again, it looked like it was intermittent before.
--
“Any claim that the root of a problem is simple should be treated the same as a claim that the root of a problem is Bigfoot. Simplicity and Bigfoot are found in the real world with about the same frequency.” – David Wong


Gertie

@rogers.com
reply to rnijmeh
As near as I can tell, whenever I've had to research such issues for clients in the past - (site not coming up or outdated site showing after a server move) - with Rogers and Shaw notably, they appear to hang on to cached info longer than some ISPs. Some ISPs are quicker to dump and do fresh lookups - sometimes a long TTL is involved - i.e. your DNS record tells the ISP they can lookup less frequently because the info is to be considered stable. But there are other times, regardless of a lowered TTL (24hrs) that had been in place for 2-3 weeks prior to a move, I've had clients pulling up their old pages still 5-7 days after a DNS change (all cached info purged from browser). Any "web accelerator" services may also be caching the bad/outdated content.