DNS problems re channels

AmoebaFrank said:
My connection has been off a couple of days now. Quick Google on my server FQDN address and I found an IP address for it. Amended my newcamd.list to use the IP rather than the FQDN and I'm back online!
 
My connection has been off a couple of days now. Quick Google on my server FQDN address and I found an IP address for it. Amended my newcamd.list to use the IP rather than the FQDN and I'm back online!

Interesting. Did you just enter the domain name of the server into something like http://get-site-ip.com/ and replace the domain name by the associated IP address in the file?

I guess you have to watch out for your supplier changing the external IP of the server, in case they do when they end up changing their domain name...

Presumably the "ban" is instigated by ISPs, since they usually specify (in the routers) their own DNS servers, and it is easy for them to twiddle the address book within to blacklist domain names? If that is the case, another (perhaps more comprehensive) alternative is to simply change the DNS server employed, either by changing it to e.g. Google's or OpenDNS' public DNS servers within the router (for sly e.g. see ://setuprouter.com/router/bskyb/sky-hub/dns.htm), or use vpn, proxy etc services that employ alternative DNS servers. Some people use public DNS servers simply because they believe they are faster.

Are the "banned servers" within http://www.ukispcourtorders.co.uk/ (assuming the list is up to date)? Afaict, the way these sites are banned is technologically ineffective for anyone who has vpn.

I might have misunderstood what the mechanism/issue is. If not I must say line servers changing their domain names seems an odd (albeit perhaps understandable as relatively easy for some, if not most) solution to me, because it is not difficult for the ISPs to track down new domain names as they arise, and adjust the DNS lookup in their own DNS servers accordingly - it is easy to play the cat, in such a cat and mouse game.

Cheers!
 
Interesting. Did you just enter the domain name of the server into something like http://get-site-ip.com/ and replace the domain name by the associated IP address in the file?

I guess you have to watch out for your supplier changing the external IP of the server, in case they do when they end up changing their domain name...

Presumably the "ban" is instigated by ISPs, since they usually specify (in the routers) their own DNS servers, and it is easy for them to twiddle the address book within to blacklist domain names? If that is the case, another (perhaps more comprehensive) alternative is to simply change the DNS server employed, either by changing it to e.g. Google's or OpenDNS' public DNS servers within the router (for sly e.g. see ://setuprouter.com/router/bskyb/sky-hub/dns.htm), or use vpn, proxy etc services that employ alternative DNS servers. Some people use public DNS servers simply because they believe they are faster.

Are the "banned servers" within http://www.ukispcourtorders.co.uk/ (assuming the list is up to date)? Afaict, the way these sites are banned is technologically ineffective for anyone who has vpn.

I might have misunderstood what the mechanism/issue is. If not I must say line servers changing their domain names seems an odd (albeit perhaps understandable as relatively easy for some, if not most) solution to me, because it is not difficult for the ISPs to track down new domain names as they arise, and adjust the DNS lookup in their own DNS servers accordingly - it is easy to play the cat, in such a cat and mouse game.

Cheers!

I just Googled my server address (out of vain hope) and it was referenced on www.freecline.com showing the IP address. I tried various DNS history sites but they contained nothing. Sites like http://get-site-ip.com resolve it to to it's current address 127.0.0.2 which is just a loopback address hence why it's not working.

My supplier just uses a free DDNS service for the hostname, I suspect this is common place so he could just setup a new one but it would require reissuing the line information. He is mailing me later today with the 'official' solution. Obviously using the IP address is unstable long term if the address does change but at least it keeps me working for now. But it does show they have not targeted the actual host and blocked the IP ranges (currently!)
 
I just Googled my server address (out of vain hope) and it was referenced on www.freecline.com showing the IP address. I tried various DNS history sites but they contained nothing. Sites like http://get-site-ip.com resolve it to to it's current address 127.0.0.2 which is just a loopback address hence why it's not working.

My supplier just uses a free DDNS service for the hostname, I suspect this is common place so he could just setup a new one but it would require reissuing the line information. He is mailing me later today with the 'official' solution. Obviously using the IP address is unstable long term if the address does change but at least it keeps me working for now. But it does show they have not targeted the actual host and blocked the IP ranges (currently!)
I got that same ip number 127.0.02 but when swapped it with the host name I get no joy any idea if im entering it wrong
 
I just Googled my server address (out of vain hope) and it was referenced on www.freecline.com showing the IP address. I tried various DNS history sites but they contained nothing. Sites like http://get-site-ip.com resolve it to to it's current address 127.0.0.2 which is just a loopback address hence why it's not working.

My supplier just uses a free DDNS service for the hostname, I suspect this is common place so he could just setup a new one but it would require reissuing the line information. He is mailing me later today with the 'official' solution. Obviously using the IP address is unstable long term if the address does change but at least it keeps me working for now. But it does show they have not targeted the actual host and blocked the IP ranges (currently!)

Tried this method Frank and got mine working, nice one
 
He seemed to help U he's ignoring me.

Keith, if you have your old details and you now have the new host. On a f5s do this menu> ok on camds setup> ok on either mgcam plugin setup or cccam client> Ok on manage and configure > ok on either cccam.cfg or if you ok'd on mgcam it will be newcamd.
Here you will see all your details, all you are doing is putting the same connection details in with the new host
 
Keith, if you have your old details and you now have the new host. On a f5s do this menu> ok on camds setup> ok on either mgcam plugin setup or cccam client> Ok on manage and configure > ok on either cccam.cfg or if you ok'd on mgcam it will be newcamd.
Here you will see all your details, all you are doing is putting the same connection details in with the new host
Manage to do it thanks for your help.
 
I just Googled my server address (out of vain hope) and it was referenced on www.freecline.com showing the IP address. I tried various DNS history sites but they contained nothing. Sites like http://get-site-ip.com resolve it to to it's current address 127.0.0.2 which is just a loopback address hence why it's not working.

My supplier just uses a free DDNS service for the hostname, I suspect this is common place so he could just setup a new one but it would require reissuing the line information. He is mailing me later today with the 'official' solution. Obviously using the IP address is unstable long term if the address does change but at least it keeps me working for now. But it does show they have not targeted the actual host and blocked the IP ranges (currently!)

That is interesting. If the IP address in freecline.com works, then it is quite possible that the server's IP address was never changed. I wonder:
a) what does the reverse IP lookup (http://ping.eu/rev-lookup/) with the address is showing, and/or
b) if the new 'official' solution is a new domain name then is it the same as the result in a) and pointing to the same IP address, although it would not necessarily prove anything if it does not.

I also wonder if the old domain name pointing to a 127 loopback was forced on the line server as the result of being "banned", or self imposed as part of restarting the service with a new domain name. Perhaps the status line from http://ping.eu/ns-whois/ can provide some clue.

I just find it difficult to believe that line server domain names have to stop functioning altogether (as opposed to being blacklisted by ISPs' DNS servers e.g.), while the domain names of bona fide "banned sites" remain alive and well to those who can bypass their ISPs' constraints.
 
Back
Top