Recent content by spydyr

Ovatvvon, Like thedaver suggested there's just too much information to put into a tek-tips post. Check out the following link. It contains all the information you need to get BIND up and running. Good Luck. http://www.zytrax.com/books/dns/

Seen this many times before and it definately looks like spyware. Along with Ad-aware you can also try spy sweeper. http://www.webroot.com/ I've run both of these programs and each one has found spyware that the other hasn't.

Ahh, I misread my CCNA book. Here's the line that confused me, "Access lists identify traffic to be filtered in transit through the router, but they do not filter traffic originating from the router". And they used telnet as the example as traffic originating from the router that can't be...

But the part that's confusing me is they are blocking snmp traffic destine for the router with an access list applied to an interface. According to this Cisco Press CCNA book I'm reading, access lists only work for traffic going THROUGH the router not destine for it.

We use Cattools. http://www.kiwisyslog.com/products.htm#cattools

Cisco is contradicting themselves, unless I'm not understanding what I'm reading. I'm preparing for my CCNA and currently reading about Access Lists. The book I'm reading specifically mentions, in a few places, that access lists are only used for traffic being routed through the router and not...

Restarting the named service always forces a transfer. But that probably won't work since transfers aren't normally working. Try turning on logging to help diagnose your problem. Add these lines to your named.conf file and restart named. logging {channel my_file { file...

You can't do this with DNS. This sounds more like a load balancer trick. Some piece of software has to run on that machine to capture requests coming over port 80, determine the url in the request and forword them to the appropriate port.

What's the point? I'm assuming you're changing the port to add security by obscurity but if you setup some mechanism to redirect 25 to 8383 it defeats the purpose of changing the port number.

Configuring iptables is a very complicated task for new users. Check out firehol. It gives you a user friendly approach to configuring iptables. http://firehol.sourceforge.net/ In regards to your email question. In the aliases file does root have an alias? You can always change the...

Dantz Retrospect also does Disk-to-Disk backups.

Did you try all the combinations to determine its not a bad PCI slot or NIC? Dell makes a diagnostic program that runs from DOS that can verify the server hardware. I would try running that also...

I'm not sure how TTL applies to the root domain servers. I'm thinking it probably won't help. You're best bet is to force a redirect either with a firewall or http. That way no traffic has a potential of being lost.

That's it.

Install adminpak.msi from the windows 2k3 cd onto your XP Pro desktop. This will install all the administrative tools that are normally found on servers on your XP machine. You can then use the DNS manager to connect to your server.