"Steven T. Hatton" wrote:
I have been using the 192.168.0.0 network space for some time now. Recently I discovered I was unable to get nslookups. I was digging around the other day with some of the bindutils and found some university was using that in a way that was visible out on the internet. I really do not understand how bind works, but I do know I have had strange behavior lately. It takes forever to contact my own systems. I have my dns configured to be the SOA for my domin, so I don't know why this would happen. The nslookup bellow shows you what I am getting. My DNS server is 192.168.0.4. The other bindutils find my server and return meaningful results that make sense in my domain.
Does anybody else run a name server for an internal network that remains connected to the internet 24x7? Do you understand what is going on here?
Hi Steve, from what you say, it sounds like a misconfigured Network "blowing" these addresses onto the internet. 192.168.0.x to 192.168.255.x are assigned for "private" networks. Same with 10.x.x.x and one 172.something network. These addresses / packets should stay inside. I use 192.168.42.x (forty.two) as private domain. No trouble yet. Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\