Baffling DNS issue via dhcp in windows.

[mresell]

I have a situation which may be totally harmless, but I find bizarre. Because it ''could be part of a non-friendly zone transfer attempt" is why I am even concerned. This can be totally harmless, but is strange. I have some theories, but am not sure. The pc in question has win98 dhcp and comcast.net broadband. Also had a dialup thru earthlink. Which was what I think started this. (Having a multihomed situation w/ dhcp.) Anyway... now the dns servers via level3.net seem to be listed in the pc and this pc wants to use them. I have specified the 2 comcast dns to try to block and have set up some FW rules. However, the pc wants to use the following dns ips. I thought about deleting the dhcp keys or the mstcp keys and redoing them. Nothing is mapped anywhere that I can find. Comcast nor Earthlink have no clue. No surprise there. Since comcast and att merged they seem to less about there network,if that's possible, but I haven't seen this on some others similiar setups, altho I have only checked a few. I did find some obscure references about these ips via google, but not too much help. I also reported the constant lookups hitting the FW to level3.net, just in case, but never heard anything. Some organizations have listed them as an abuser. Any ideas or suggestions about this? Is level3 just being aggressive w/ their dns management?

209.244.0.4
209.244.0.3

[mresell]

Well for anyone that cares. I finally got rid of the pesky things. Because there is a limit to networking tools in 98, I had to remove tcp/ip then reinstall ,which appeared to kill them. The dial-up does not have tcp/ip for the moment until that can be setup more securely. Not needed anyway at the moment. The dns definitely came in thu earthlink dialup, but it doesn't belong to them. Other dialup isp's use those dns tho. Hopefully, the firewall will keep it out, until hopefully, it goes away. The sad thing is that the fix was easy, but none of the tech's at any of these isps even suggested it.