Victor Waites
New Member
- Impact
- 1
I have a domain name that can't be reached on one major cellphone network and it's subsidiaries. What could be the issue?
I have a domain name that can't be reached on one major cellphone network and it's subsidiaries. What could be the issue?
I'm asking, because I don't have a clue. The domain register explained to me that everything was working just fine, and I thought maybe it could have been my phone, but that wasn't it. I tried requesting that same domain on a different phone, with a different cellular company, on the same network and I experienced the problem. What I would like know is who should I contact about this, because something is wrong and I am being kicked down the road. It's like a mechanic taking advantage of a woman who has no knowledge of how an engine works.Now that's a really broad question. It could be on a DNS blocklist. On a proxy blocklist. There could be routing issues. TCP/IP issues. The website can block CIDR ranges. Other issues. It could be anything, but you have to be more specific.
How about domain name resolution
Hey, I'll look into all of theses ideas. Thanks guys. I just needed some where to start.How about domain name resolution
My reason for asking the question was to find out who would be responsible and how do I get it fixedMost domains work with mobile browsers one thing about mobiles overlooked is how gtlds work in sms. It is quite easy to accidently create a link. Eg two.words with a dot between them.
My reason for asking the question was to find out who would be responsible and how do I get it fixed
Thank you.The domain might be flagged as adult content on a list that the mobile network uses, you can try using unblocked.org.uk to see if the domain is being blocked or not and submit it for approval there too
My ip address has been changing.Same IP.
What type of error do you get?
Clear DS records for domain and it will work. I'm betting you just transferred from one registrar to different registrar. The old registrar is the culprit - they entered DS records.. When transferred, this garbage is still there. Clear out this record and it will work. This DS record is a way that the old registrar tries to control the action of your URL.
DS (DNSSEC) records.... NOT TO BE CONFUSED WITH DNS.
This was going onClear DS records for domain and it will work. I'm betting you just transferred from one registrar to different registrar. The old registrar is the culprit - they entered DS records.. When transferred, this garbage is still there. Clear out this record and it will work.
DS (DNSSEC) records.... NOT TO BE CONFUSED WITH DNS.
I didn't want to make the names public until I was sure of what was happening.Without the exact domain name, the name of the telecom provider, their DNS resolvers, the source IP and perhaps NAT port, destination IP, website specifics, it's really difficult to answer your question. We cannot say who is responsible here without this information. The only thing I would suggest is: find a local nerd to test and debug a few things for you