Ooops! My domains are all down!
 

Sorry folks.. I had a bit of a bandwidth issue and am working with my host to get back up online as quickly as possible. I got hit hard by a group of Chinese search engines and it drove my bandwidth crazy.

Domains impacted:

• eroticove.com
• lezzietown.com
• pervertedpagan.com
• rearentrylovers.com
• mykinkmachine.com
• fattypatrol.com
• freecunthunter.com

And my blog, Silky's Delight at silky.pervertedpagan.com

Sigh...

update - eroticove.com and lezzietown.com are being loaded right now onto a different host. rearentrylovers.com is already working in some areas. Just holding on domain name propagation. Thanks for your patience, everyone!

This isnt much help right now, but going forward you might want to sepererate your nameservers from your hosts. That will allow you to just change IP adresses to the new host instead of waiting until your registrar transfers control of the DNS to the new host, then waiting while the hosts DNS propagates throughout the intertubes.

I will handily recommend using nothing but afraid.org for nameservers. It gives you utter and complete control over where your domain names point, the interface is easy to use and they resolve really quick.

Further, afraid.org is one of the genuinely free services available on the internet that hasnt turned into a spam-o-rama, and is exactly the same as it was around 1999 when I built my first naked teenager site. The guy that runs it does it because he wants to, not because he's a greedy dick of a corporation trying to angle in on a nickle or dime here and there.

I can move a domain and it will resolve to the new servers in about a half hour from the minute I decide to make the move. If its a new domain, it will resolve in 5 minutes from my experience.

Also, you can add or delete secondary nameservers as often as you see fit.

Also, since you are having bandwidth issues, you might be interested that cyberwurx still has there "double bandwith" special on unmanaged servers. Buy 500 gigs a month, get 500 free. Keep in mind unmananged means you get a server with SSH and nothing else, you build up what you want from there (and you can set the firewall to block all the chinese IP addresses too), OTOH if you arent willing to learn some linux admin, you wont be able to do it. Their prices are absurdly low for this. Also, their support is the best in existence. You can look them up on the net, or I can give you my code so I can get a few dollars. Either way is fine with me.

I've always wondered how much affect the nameserver has on the time it takes to resolve. I haven't done enough transfers to really know for sure, but GoDaddy seems to take much longer than Namecheap, from my very limited experience. I didn't know that was something the nameserver had any control over.

I see your stuff is still down this morning. :(

They are all loading fine here, except for freecunthunter, in Upstate NY.

Just checked and I'm still getting 500 errors on her stuff with this message.
Bandwidth Limit Exceeded

The server is temporarily unable to service your request due to the site owner reaching his/her bandwidth limit. Please try again later.
Apache/1.3.37 Server at www.lezzietown.com Port 80

I only get that message for the last domain in her list which is still pointed at her old nameservers. The others, which are now pointed to Colo-cation, all work fine for me. |huh

All working for me now, even lezzietown.com.

Here in fl on comcast as UW sees all are up but the last

Well, thats cause all the cunt in NY State has a price. |nahnah|

all up here except the last one has exceeded bandwidth.


Then again, I having a caching dns (dnsmasq) in my room that pulls from 7 big dns servers, so mostly everything resolves well here. Our ISP's dns server goes down 3 or 4 times a year, so I dont use it at all. It must be on a sun box... LOL.

I just repointed the critical ones. Freecunthunter doesn't have any freesites or galleries on it at this time. It is a project waiting to happen.

Nameservers can take anywhere from minutes to about 24 hours to do. That does seem to be about right, and I have seen it be about the same no matter who you use for a registrar.

The good news is it seems to be a hotlinking issue, which I don't understand very well. I had the anti-hotlinking turned on, and always have. Apparently the little goofs know how to get around me. UW, Sparky is as good as y'all have been saying, and I will highly recommend him to anyone who will listen. That's not saying my current host is bad. My host is currently unavailable or this problem would have never happened. I know it will be resolved in just a few more days.

Thank you all so much for your help, advice and kindness.

I think there are like 10 or 12 sets of root nameservers, and everything propogates from them. So your new address has to go to them, then get propogated out to the millions of other dns servers like the one your browser talks to for resolving. Sometimes those guys cache longer than they should instead of obeying the ttl in your zone records. You cant really force that, but if you control the numbers instead of waiting for your host to do it for you, you can speed it up a little.

I think afraid has been around so long they are hardwired to the root nameservers.

A new domain will resolve pretty quick because the roots dont know where it is and haven't passed on any information to ISPs, so the ISPs dont have them cached and will ask upstream which will then ask the various registrars and return an answer. No cache means a little slower response, but not 3 hours slower.

Its pretty technical. CD34 will show up soon, make me look stupid and answer your question the right way.

DNS and Registrars
 

When a surfer clicks on a link to, say, pornurl.org, the following occurs:

1. The surfer's computer checks its hosts file. Is there an entry there? Of course, there rarely is.
2. The surfer's computer then checks with its DNS server as defined in its network settings.
3. The DNS server checks to see if it is authoritative for the domain. If so, it provides the data. Of course, this is also rarely the case. (It would only be the case if your surfer's DNS server happened to be that of the company hosting your domain. For practical purposes, this just doesn't happen).
4. If the server is not authoritative, it determine if it has data cached for the given domain. If you've ever wondered about those TTL, Refresh, Expires, etc. settings for your DNS, those control this behavior. While we like to set short refresh values, so that hosting changes propagate immediately, you should keep in mind that if you have a longer value, DNS servers can cache the data longer, meaning they're more likely to be able to give a response right here ... without going through additional steps.
5. If the server is not authoritative and has no data cached, then it looks for the name server for the top level domain (.com, .net, .org, .us, etc.). It queries this server for the name servers of your domain. The root server replies, providing your domain's DNS servers IP addresses.
6. The server contacts your DNS server, requesting the IP address of your site. If your first server fails to respond, it should contact additional servers whose addresses were provided in the previous step.
7. The server returns the IP address to you.

You'll notice that nowhere in here is your *registrar* contacted... unless they happen to be providing your DNS for you. The only role your registrar plays is in updating the root server with the correct IP addresses of your DNS servers. If this changes, and your registrar is slow, it will take longer for the changes to propagate, but there's no impact on live queries.

Hope this helps.

-jbn

Well in moving over sexysmutlinks and click4sexfun, they propagated to my comcast at work within a few hours, but took almost 12 hrs longer to propagate to my att u-verse at home

Down with dumb ISPs
 

This kind of behavior is generally caused by an ISP (in this case att u-verse) ignoring the refresh parameters on a domain. Some ISPs have decided "they know better" and ignore refresh values. This is frustrating as can be, and one of the reasons I run my own DNS server at home. This can have unintended consequences. During the Super Bowl, nfl.com generally gets changed to point to akamai. It gets changed back promptly thereafter. Customers of bad ISPs (AOL was notorious for this) get stuck on the "slow" server while customers of good ISPs are on the fast akamai cache.

-jbn

A cool trick to do with your hosts file is set up a virtual host on your server that isnt in your zone records, but is in your host file. The sub is unreachable unless someone can guess the subdomain name (and it doesnt even have to be a real domain name, "somenameimadeup" will work fine). Its a good way to set up phpmyadmin for instance. You still want a good root password for mysql, but it adds a layer of obfuscation.

Also, if you are initially building a site, you can use your host file instead of a nameserver so it doesnt go live on the internet until you are ready, but will still answer to its domain name from your computer. Thats handy for setting up wordpress. Its also handy if you want to work on a domain before it resolves to your ISPs dns.

Best of all... its a great way of blocking experts-exchange.com if you cant do it on your router. I really hate that site.

I had one that was using jscript on the client's computer to steal the bandwidth. That will render your .htaccess (aka hotlink protection) useless unless you block blank referrers. You can beat them though if the page with the thumbs is php by using 6 lines of PHP to write the user's host IP address to a deny/allow directive in your .htaccess for that directory. IOW, if they dont hit your PHP page, they dont get the pictures. end of story. add in the normal hotlinking protection and at that point, all the hotlinker can do is open your page in a frame, which is good for you because it's free advertising. Give him a day of that then add a framebusting jscript and you are now stealing his traffic every time he tries to use your page.