> Has anyone had trouble with the new Packard bells, 1.5 years or newer, and
> dns?
In a word, yes. From what I heard, PB got a bad build of Win95, and
it wound up on millions of machines that hit the market in time for
the Christmas season last year. We were deluged with them.
Depending on how they are configured, they send out malformed DNS
queries, or they send out repeated queries with the local domain
suffix without ever sending the next-stage request without the local
domain suffix.
The sequence with xyz.com configured as the local domain should be
1. ask primary server to resolve www.microsoft.com.xyz.com
2. ask primary server to resolve www.microsoft.com
These systems will
1. ask primary server to resolve www.microsoft.com.xyz.com
2. ask secondary server to resolve www.microsoft.com.xyz.com
3. ask primary server to resolve www.microsoft.com.xyz.com
4. ask secondary server to resolve www.microsoft.com.xyz.com
5. ask primary server to resolve www.microsoft.com.xyz.com
6. ask secondary server to resolve www.microsoft.com.xyz.com
Without a local domain configured, tcpdump reports a malformed DNS
query.
-- Dick St.Peters, stpeters@NetHeaven.com Gatekeeper, NetHeaven, Saratoga Springs, NY, 1-800-910-6671 (voice) Albany/Saratoga/Glens Falls/North Creek/Lake Placid/Blue Mountain Lake Soon: Elizabethtown/Greenwich/Keene/Plattsburgh/Saranac Lake/Ticonderoga First Internet service based in the 518 area code