It's supposed to. Google owns YouTube. It detects what you entered as the url (youtube.com or www.youtube.com) then takes you to the correct data on the cache server. I.e. it only works through the hosts.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Did you buy your last car with cash or on a finance plan?
Tutorial: Fix Afrihost YouTube problems (10/12/14)
- Thread starter giggity
- Start date
It's supposed to. Google owns YouTube. It detects what you entered as the url (youtube.com or www.youtube.com) then takes you to the correct data on the cache server. I.e. it only works through the hosts.
True but I think there's some reason you should not, can't remember why.
Is this still applicable ? Do I need to change my settings back to the way it was since AF fixed it or can I leave it as it is?
Why is this not a default option, what is the Pro's and Con's of doing this manual adjustment?
( Sorry for all the questions just curious )
Why is this not a default option, what is the Pro's and Con's of doing this manual adjustment?
( Sorry for all the questions just curious )
You can leave it as is if you want. Try between the two (with and without) and see which is faster. I kept mine with this since it was faster for me.
It's not simply an option, because it's a system-level tweak to manually adjust DNS. The average person wouldn't use it. But it really isn't complicated.
Pros: YouTube worked whilst Afrihost was having problems.
Cons: Takes time? Idk.
GarethY
Well-Known Member
Pros:
1. It works
Cons:
1. Static DNS records are a bad, bad idea. If the IP address changes several years down the line, then you will tear your hair out trying to figure out why youtube doesn't work anymore.
2. Deployment on a large network. I have a lot of computers on my business network and I'm damned if I'm going to do this on each and every one of them, just because Afrihost's network doesn't work.
Seriously, it's ridiculous to have to expect end users to make a tweak like this.
1. It works
Cons:
1. Static DNS records are a bad, bad idea. If the IP address changes several years down the line, then you will tear your hair out trying to figure out why youtube doesn't work anymore.
2. Deployment on a large network. I have a lot of computers on my business network and I'm damned if I'm going to do this on each and every one of them, just because Afrihost's network doesn't work.
Seriously, it's ridiculous to have to expect end users to make a tweak like this.
Valid point thank you for the help
Static DNS isn't that bad of an idea when the IP address hasn't changed in over four years. Then just remember "oh yeah my hosts file is altered". It's a tweak I used to use nearly all the time for local cap tricks.
You could write a script to do this for a network quite easily. Just a for loop that creates and copies the file on each system -- assuming your network is set up correctly and you have major admin privileges.
Wasn't "expected"... Just a workaround from a user which works.
Last edited:
The specified URL's should load a bit quicker because you are bypassing the DNS server.
2. On a large network you should be running your own internal DNS servers. Just set it there so all the network computers get the update without having their host file set.
GarethY
Well-Known Member
I am and I tried that, but this is what I got:
http://mybroadband.co.za/vb/showthread.php/665929-Tutorial-Fix-Afrihost-YouTube-problems-(10-12-14)?p=14169683&viewfull=1#post14169683
Oh ok. If you don't connect https but http it will work.
You might need to look at stackoverflow how to set up the local DNS so that it works with secure sites that share the same ip.