I run a DNS server for around 470 domains. I have this problem with our telco/dsl provider(Large Canadian Monopoly). What i found is if the TTL is set to less than 3 hours it is automaticly reset to 3 weeks. As a result I have set all of out TTLs to at least the 3 hour minimum.
Been using slackware from day one, looks like it's finally time to move on.
-- Exploiting Windows is like stealing candy from a baby.
Looks like you have never tried to take candy from a baby.
I run a DNS server for around 470 domains. I have this problem with our telco/dsl provider(Large Canadian Monopoly).
What i found is if the TTL is set to less than 3 hours it is automaticly reset to 3 weeks.
As a result I have set all of out TTLs to at least the 3 hour minimum.
As a network admin for a small ISP I found a simple work around.
/sbin/ifconfig eth0:1 64.94.110.11 netmask 255.255.255.255
/www/nodns
First I set up a webserver.
add to apache
<VirtualHost 64.94.110.11>
DocumentRoot
ServerName A.com
ErrorLog logs/nodnserror.log
CustomLog logs/nodns.log common
</VirtualHost>
Set up a webpage for this server.
on my cisco I set up the following route
ip route 64.94.110.11 255.255.255.255 xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the real ip of my server.
They tried it in Guelph Ontario in 1996. It was called MONDEX then. It failed.
l
http://www.efc.ca/pages/media/globe.01nov98.htm
I just had a server chash real bad at exactly
00:00 GMT Jan 1 2001. Could be a coincidence.