But that might be because my sysadmin doesn't do DNS checks at the SMTP server...
Especially mail with the From header set to a Hotmail address is often spoofed. Unfortunately, this address might exists and the owner can't help it. As for hotmail, spoofs are easy to filter out without actually parsing the Received headers. But if I feel like replying or sending abuse mail, I *always* parse the received headers.
At the last job I had, it took 3 MSCEs 2 days to get my password changed on a single NT server.
Funny, I had to do this recently and it took me ten minutes of googling to figure that out. I didn't go for the official solution though. I downloaded a Linux bootdisk that did all the work for me...
DNS is decentralized, in the sense that no server holds all information, but servers only hold information for a certain part of the domain-space. However, *no server can cache all information*, and to answer queries, these servers must ask other servers. And to know which servers are authoritive for a certain domain, you'll have to ask the root servers. This makes DNS pretty centralized in the end. And vulnerable.
Their 'campus'webserver (http://www.snt.utwente.nl/) has some information on their network.
They installed a 55Mb uplink to a company nearby the night after the fire, but this was through a masquerading server. Thursday night they have started connecting all buildings to SURFnet (so they would have official IP-addresses and stuff), still through the 55Mb link. The campus was last on Friday. They are repeatingly asking the students not to download large files.
They expect to get a full 1Gb uplink tomorrow afternoon.
I don't know what they did with the Debian servers, though.
Slashdot Mirror
But that might be because my sysadmin doesn't do DNS checks at the SMTP server... Especially mail with the From header set to a Hotmail address is often spoofed. Unfortunately, this address might exists and the owner can't help it. As for hotmail, spoofs are easy to filter out without actually parsing the Received headers. But if I feel like replying or sending abuse mail, I *always* parse the received headers.
DNS is decentralized, in the sense that no server holds all information, but servers only hold information for a certain part of the domain-space. However, *no server can cache all information*, and to answer queries, these servers must ask other servers. And to know which servers are authoritive for a certain domain, you'll have to ask the root servers. This makes DNS pretty centralized in the end. And vulnerable.
Their 'campus'webserver (http://www.snt.utwente.nl/) has some information on their network.
They installed a 55Mb uplink to a company nearby the night after the fire, but this was through a masquerading server. Thursday night they have started connecting all buildings to SURFnet (so they would have official IP-addresses and stuff), still through the 55Mb link. The campus was last on Friday. They are repeatingly asking the students not to download large files.
They expect to get a full 1Gb uplink tomorrow afternoon.
I don't know what they did with the Debian servers, though.
My provider seems to have old DNS data cached, the link doesn't work. Try their IP-address instead.