peter vander kleut <[EMAIL PROTECTED]> schrieb: >Thanks for your answer, Lars >I thought of that too but I used "computername.private.network" >purely >descriptive in my first mail, what I use in my network is >*name*.*domain*.com, but since this is a nat box, until this afternoon >when >I ask any outside website I get the external IP adress of my bering >box >returned, and my internal domainshould be shielded by >bering/shorewall >rules. I am deeply concerned about network adresses in my private >network >all of a sudden changing to public adresses depending on whether I >have >internet access or not. Bering "knows" which ip's belong to my private >net >192.168etcetera, why would it allow this traffic thru in either >direction? >The XP box uses the dnscache of the bering box so it has AFAIK no >business >with verisign, I has a hard coded Ip (NO DHCP)
Any unknown *.com and *.net address get resolved to 64.94.110.11, since verisign changed their nameservers. Your dns server installed on the bering box is talking to the verisign nameserver for any *.com or *.net address. Just change the dns name of your local net to *.loc or *.nl and you are fine. Cu -- written with FeLaMiMail need Groupware => http://www.egroupware.org ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
