Webspace

S

sneaky

Active Member
Joined
Mar 1, 2004
Messages
39
Reaction score
0
Location
.
Anyone got any idea if Sentech will throw a couple of meg's worth of webspace to their users sometime in the foreseeable future? Think almost all broadband SP's provide some why not them?

________________________
Must think happy thoughts about the antenna!!!
 
Install netbios and file and print sharing protocolls.
And phone everyone when your ip changes ;)

For R200 a year, you could get dynamic ip hosting, now all you add is a domain name. Considering this is wireless, it should be less stable than a permanent line (unless hosted by telkom), and theyre spoiled.
It's nice having your own domain name.

What I would like from sentech is reverse ip lookups or whatever
so my ip resolves to my hostname. Now that would be a nice service.
Extra 300 a year ? hehe
 
i have my own domain name, hosted offsite etc. I tried organizing with the guy to maybe allocate home.acidrazor.com or something to my dynamic IP address, and update that as soon as it changes (like dyndns)

He said it would slow the system down considerably (seeing as they have their own DNS servers too), and optimum update times are usually 7 hours for a DNS change? (could be set to 1 minute)

What can I suggest to him to implement on his side?
 
set the expiry time of the dns to 24 hours.
When your connection drops amd you reconnect, it takes under 10 minutes to update your ip, if not seconds.

The amount of bandwith would be so little, they wouldnt notice, and theire systems wouldnt suffer a bit, unless you are hosting google.com.

Anyways, if they all iggy about it, just goto dynds or whatever.
160 a year aint bad
 
er... okay, how can i tell HIM that (does he set the expiry for home.acidrazor.com to 24 hours? how does it update?)
 
No, leave the refresh/ttl as is.
All you/he need to do is change the TTL just for that one entry in the zone file. I set mine to 10 seconds.

It's as simple as:
$TTL 10 ; 10 seconds
mybox A 66.18.x.x
$TTL 28800 ; 8 hours

The second TTL you should set to the same as the TTL before you changed it to 10 secs


--
 
Just, as a DNS admin can I inject some sanity at this point.

The reason TTL's exist is sothat the internet is not consumed by DNS traffic. Every time you visit a site or connect to anything on the internet it generaly looks up the reverse (PTR record) for the connecting IP (gethostbyaddr)

"set the expiry time of the dns to 24 hours. When your connection drops amd you reconnect, it takes under 10 minutes to update your ip, if not seconds."

I'll say this quite simply, thats absolute horse ****. ok.

If the TTL is 24h and it gets cached, the forward resolution for that domain will be vaild for 24 hours, update all you like untill you are blue in the face the rest of the world will see trxtr.doesnt.understand.dns.com as 127.0.0.1 or whatever for 24 hours.

No sane admin would allow a TTL of lower, a DNS server would become quickly over run with requests.

There is a simple demonstration and that is to disable cacheing and to run "trafshow" or something and the instant a few connection's start you will see *millions* of DNS servers arround the globe connecting to your PC to resolve incoming IP addresses (and MUCH worse if you were trying to have some kind of dynamic PTR record which wouldnt actualy work anyway unless the IP was static for a *long* period of time)

To show the extent of that, see just a simple DNS tree for this site.

<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">
Tracing to www.myadsl.co.za via A.ROOT-SERVERS.NET, timeout 15 seconds
A.ROOT-SERVERS.NET [.] (198.41.0.4) *
|\___ NS-EXT.VIX.COM [za] (204.152.184.64)
| |\___ ns0.plig.net [co.za] (195.40.6.40)
| | |\___ dns7.webonline.biz [myadsl.co.za] (196.7.217.133) Got authoritative answer
| | \___ dns2.webonline.biz [myadsl.co.za] (196.25.84.199) Got authoritative answer
| |\___ ns0.coza.net.za [co.za] (206.223.136.195)
| | |\___ dns2.webonline.biz [myadsl.co.za] (196.25.84.199) (cached)
| | \___ dns7.webonline.biz [myadsl.co.za] (196.7.217.133) (cached)
| |\___ ns0.is.co.za [co.za] (196.4.160.17)
| | |\___ dns2.webonline.biz [myadsl.co.za] (196.25.84.199) (cached)
| | \___ dns7.webonline.biz [myadsl.co.za] (196.7.217.133) (cached)
| |\___ ns4.iafrica.com [co.za] (196.7.142.131)
| | |\___ dns2.webonline.biz [myadsl.co.za] (196.25.84.199) (cached)
| | \___ dns7.webonline.biz [myadsl.co.za] (196.7.217.133) (cached)
| |\___ ns2.coza.net.za [co.za] (160.124.16.145)
| | |\___ dns7.webonline.biz [myadsl.co.za] (196.7.217.133) (cached)
| | \___ dns2.webonline.biz [myadsl.co.za] (196.25.84.199) (cached)
| \___ ns1.coza.net.za [co.za] (66.139.79.204)
| |\___ dns2.webonline.biz [myadsl.co.za] (196.25.84.199) (cached)
| \___ dns7.webonline.biz [myadsl.co.za] (196.7.217.133) (cached)
|\___ UCTHPX.UCT.AC.za [za] (137.158.128.1)
| |\___ ns4.iafrica.com [co.za] (196.7.142.131) (cached)
| |\___ ns2.coza.net.za [co.za] (160.124.16.145) (cached)
| |\___ ns1.coza.net.za [co.za] (66.139.79.204) (cached)
| |\___ ns0.plig.net [co.za] (195.40.6.40) (cached)
| |\___ ns0.coza.net.za [co.za] (206.223.136.195) (cached)
| \___ ns0.is.co.za [co.za] (196.4.160.17) (cached)
|\___ RAIN.PSG.COM [za] (147.28.0.34)
| |\___ ns0.plig.net [co.za] (195.40.6.40) (cached)
| |\___ ns0.coza.net.za [co.za] (206.223.136.195) (cached)
| |\___ ns0.is.co.za [co.za] (196.4.160.17) (cached)
| |\___ ns4.iafrica.com [co.za] (196.7.142.131) (cached)
| |\___ ns2.coza.net.za [co.za] (160.124.16.145) (cached)
| \___ ns1.coza.net.za [co.za] (66.139.79.204) (cached)
|\___ NS.RIPE.NET [za] (193.0.0.193)
| |\___ ns4.iafrica.com [co.za] (196.7.142.131) (cached)
| |\___ ns2.coza.net.za [co.za] (160.124.16.145) (cached)
| |\___ ns1.coza.net.za [co.za] (66.139.79.204) (cached)
| |\___ ns0.plig.net [co.za] (195.40.6.40) (cached)
| |\___ ns0.coza.net.za [co.za] (206.223.136.195) (cached)
| \___ ns0.is.co.za [co.za] (196.4.160.17) (cached)
|\___ MUNNARI.OZ.AU [za] (128.250.22.2)
| |\___ ns0.is.co.za [co.za] (196.4.160.17) (cached)
| |\___ ns4.iafrica.com [co.za] (196.7.142.131) (cached)
| |\___ ns2.coza.net.za [co.za] (160.124.16.145) (cached)
| |\___ ns1.coza.net.za [co.za] (66.139.79.204) (cached)
| |\___ ns0.plig.net [co.za] (195.40.6.40) (cached)
| \___ ns0.coza.net.za [co.za] (206.223.136.195) (cached)
|\___ MUNNARI.OZ.AU [za] (128.250.1.21)
| |\___ ns4.iafrica.com [co.za] (196.7.142.131) (cached)
| |\___ ns2.coza.net.za [co.za] (160.124.16.145) (cached)
| |\___ ns1.coza.net.za [co.za] (66.139.79.204) (cached)
| |\___ ns0.plig.net [co.za] (195.40.6.40) (cached)
| |\___ ns0.coza.net.za [co.za] (206.223.136.195) (cached)
| \___ ns0.is.co.za [co.za] (196.4.160.17) (cached)
|\___ HIPPO.RU.AC.za [za] (146.231.128.1)
| |\___ ns2.coza.net.za [co.za] (160.124.16.145) (cached)
| |\___ ns1.coza.net.za [co.za] (66.139.79.204) (cached)
| |\___ ns0.plig.net [co.za] (195.40.6.40) (cached)
| |\___ ns0.coza.net.za [co.za] (206.223.136.195) (cached)
| |\___ ns0.is.co.za [co.za] (196.4.160.17) (cached)
| \___ ns4.iafrica.com [co.za] (196.7.142.131) (cached)
\___ AUTH00.NS.UU.NET [za] (198.6.1.65)
|\___ ns4.iafrica.com [co.za] (196.7.142.131) (cached)
|\___ ns2.coza.net.za [co.za] (160.124.16.145) (cached)
|\___ ns1.coza.net.za [co.za] (66.139.79.204) (cached)
|\___ ns0.plig.net [co.za] (195.40.6.40) (cached)
|\___ ns0.coza.net.za [co.za] (206.223.136.195) (cached)
\___ ns0.is.co.za [co.za] (196.4.160.17) (cached)
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

all of those lookups are of course eliminated by simply checking the cache on your ISP's upstream DNS. This is the entire point of the DNS system.

By all means, use a dynamic DNS service and keep your TTL arround 2h which is fine. Some free ones include zoneedit.com etc.

<hr noshade size="1">
"Since light travels faster than sound, people appear bright until you hear them speak."

NetLink Research
 
dynamic DNS providers do EXACTLY what I described there.
The zone itself sits with a normal TTL to prevent flooding, but the dynamic DNS entry (with the low TTL) will be requested from the primary/secondary DNS servers whenever someone wants to use it.

noone, I'd mail you, but my thunderbird is currently acting up (won't open, just a blank window)
You'll have a domain zone file, in the zone file there will be an A record with your home.acidrazor.com entry.

it'll look like this:

home A 66.x.x.x (what ever your IP address is at the time)

you need to put the $TTL around this entry..so it'll be:

$TTL 10
home A 66.x.x.x
$TTL 28800

then your DNS provider needs to give you some way of updating this entry when your IP changes. This can be done with a simple .php script that you send your details to (make sure this is authenticated)

eg. https://user:p[email protected]/updatedns.php?zone=acidrazor.com&entry=home&ip=yournewIP

updatedns.php should have the logic to replace this entry in the file and update the serial number of the zone file. One very easy way, if the provider use bind, is to use the update command of Net::DNS in perl, this takes care of changing the entry, updating the serial and sending update to the slave servers.

Hope that helps [:)]

--
 
Um, how exactly does having a high SOA TTL and a low TTL for the A record actualy make any difference? You're still requesting the A record.

Whatever, I give up, go kill your servers with DNS traffic, it isnt my problem. Dont cry here when it buggers up.

<hr noshade size="1">
"Since light travels faster than sound, people appear bright until you hear them speak."

NetLink Research
 
dude, i've been using this for a few years now...

go sign up for a dyndns.org or whatever account, and do a dig on your dynamic entry, check the TTL they normally use 60 seconds

--
 
Does anyone know if I have a router, and the PC is shutdown, if the modem would stay connected? That way I could keep my IP static, unless I lose power for a long period of time...
 
When I had the router working it stayed connected while my pc was rebooting or shut down.
 
mmmmmmmkay[?], I was thinking more along the lines of a couple of megs on a SENTECH server so that static IP addresses dont play a roll, just get an FTP proggy with your username and password and kaching.[8D] Now dont you thik that would be a nice gesture from our friends at SENTECH.[:D]

________________________
Must think happy thoughts about the antenna!!!
 
As you all know ... dont trust administrators.

They come out of meetings and...
get all pissed off with you.

Anyways, from my understanding the reverse for some reason just wont work (still cant get a not nonsense jargon out). Anyways, I know I can get my dynamic ip hosting locally, by a firend. But I'm not a dns andmin ... who would want to be ;) hehe.
If he's willing to offer it, and other companies willing to offer it.
Then that's cool, who cares about bringing down the internet anyway..
it's been cheduled for a reboot for many years now.
 
No one said anything about bringing down the internet, but its just a serious waste of bandwidth if you attempted to do that with a reverse IP.

<hr noshade size="1">
"Since light travels faster than sound, people appear bright until you hear them speak."

NetLink Research
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X