My DNS server is set up as a cashing server but non-local DNS requests have to be forwarded somewhere, don't they?
No. Forwarding is a feature that should normally be off by default.
The way that a caching DNS server works, it connects to the root servers and "drills down" until it reaches the DNS servers for a record that is being looked up.
Forwarding bypasses that, and instead goes to someone else's DNS server. The advantage to this is that the lookup can be slightly quicker if the information is already cached. But at about 500 bytes and 2 round trips per DNS lookup, it doesn't save that much time -- and can increase the amount of time (if the forwarding DNS server is slow) or lost packets or incorrect results (if the forwarding DNS server is flaky, or has oddball policies like Sprint/AT&T do).
One of the tabs in the DNS server properties is "Forwards" to resolve non-local requests. What do I use instead of my T-1 provider for this?
You just leave it blank. :)
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
