lame server resolving SOLUTION!!!
THE reason is people on the net are LEECHING.
They are using your server to resolve the internet instead instead of their own DNS server that their ISP gave them.
SO when they try to surf to www.cnet.com it does a lookup to find out where in the world www.cnet.com is and uses your server to resolve it.
www.cnet.com (for humans) 216.239.122.220 (for computers)
If you don’t want the rest of the world using part of your server to do lookups then follow these simple instructions.
These instructions will change your BIND configuration so it will
ONLY RESOLVE your DOMAINS and NOT the REST OF THE NET.
You NEED to KNOW your IP ADDRESSES!!!
If you already know what they are then skip steps A-H and jump to
Steps 1-18
A) Open your favorite browser to your virtualmin server.
https://your_domain.com:10000
B) Type your Login and Password
C) Top Left Click on "Webmin"
D) Left Side Click on "Networking"
E) Then Once it expands Click on "Network Configuration"
F) Click on “Network Interfaces” it’s icon is a network card
G) Write down all of the IP addresses you see.
IF You Don’t You’ll BE SORRY!
H) Click "Logout" on the bottom Left
-
Open your favorite browser to your virtualmin server.
https://your_domain.com:10000
-
Type your Login and Password
-
Top Left Click on "Webmin"
-
Left Side Click on "Servers"
-
Then Once it expands Click on "BIND DNS Server"
-
Click on “Access Control Lists” it’s icon is a lock
-
In the Small Left box type "dnssrvs"
-
In the Big Right box type Your DNS servers separated by a space.
example "74.44.441.1 74.44.441.254 62.44.441.1"
-
Click Save
-
Click on "Access Control Lists" again
-
In the Small Left box type "localip"
-
In the Big Right box type Your Private and Public IP Addresses of your server (including virtual IP addresses), separated by a space.
example "74.44.441.12 74.44.441.13 192.168.1.100"
Note: If you don’t fill in your correct ip addresses for “localip”
Your OWN SERVER won’t be able find your domains and YOU WILL
NOT BE ABLE TO VIEW YOUR SERVER’S WEB PAGES, SEND OR RECIEVE
EMAIL ANYMORE!!! Basically you will be in a world of hurt 
If you are LOST AND NEED YOUR IP ADDESSES DO STEPS A-H FIRST
(found at the TOP - you skipped that step didn’t you…)
-
Click Save
-
Click on "Miscellaneous Options" the icon is a screw driver and
a wrench
-
Find the Option titled "Do full recursive lookups for clients?"
and Choose "No" (this stops others from using your server)
-
Click "Save"
-
Click "Apply Changes" button
-
Click "Logout" on the bottom Left
OK so how do I check it?
Windows Method -
20) Start ->Run -> cmd
21) Type "nslookup -your_server_name" (PRESS ENTER)
example "mail.yahoo.com"
22) At the ">" type "cnet.com" (PRESS ENTER)
you should get:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Served by:
(This means your server said go to the ROOT servers and ask them)
- At the ">" type "your_domain" (PRESS ENTER)
example "myownserver.com"
you should get:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Name: myownserver.com
Address: 74.44.441.12
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(Your server answered ONLY A DOMAIN it is in charge of)
Linux Method
(Hard Core Command line 
)
-
Drop to a shell
-
At the "[myname@ns1]$" type "sudo dig cnet.com @127.0.0.1"
You Should get:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; <<>> DiG 9.3.4-P1 <<>> cnet.com @127.0.0.1
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30190
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 0
;; QUESTION SECTION:
;cnet.com. IN A
;; AUTHORITY SECTION:
. 3600000 IN NS A.ROOT-SERVERS.NET.
. 3600000 IN NS B.ROOT-SERVERS.NET.
. 3600000 IN NS C.ROOT-SERVERS.NET.
. 3600000 IN NS D.ROOT-SERVERS.NET.
. 3600000 IN NS E.ROOT-SERVERS.NET.
. 3600000 IN NS F.ROOT-SERVERS.NET.
. 3600000 IN NS G.ROOT-SERVERS.NET.
. 3600000 IN NS H.ROOT-SERVERS.NET.
. 3600000 IN NS I.ROOT-SERVERS.NET.
. 3600000 IN NS J.ROOT-SERVERS.NET.
. 3600000 IN NS K.ROOT-SERVERS.NET.
. 3600000 IN NS L.ROOT-SERVERS.NET.
. 3600000 IN NS M.ROOT-SERVERS.NET.
;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Oct 26 05:21:30 2007
;; MSG SIZE rcvd: 237
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(This means your server said go to the ROOT servers and ask them)
- At the "[myname@ns1]$" type "sudo dig myownserver.com @127.0.0.1"
You Should get:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; <<>> DiG 9.3.4-P1 <<>> myownserver.com @127.0.0.1
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13709
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
;; QUESTION SECTION:
;myownserver.com. IN A
;; ANSWER SECTION:
myownserver.com. 38400 IN A 74.44.441.12
;; AUTHORITY SECTION:
myownserver.com. 38400 IN NS ns3.myownserver.com.
myownserver.com. 38400 IN NS ns.myownserver.com.
myownserver.com. 38400 IN NS ns2.myownserver.com.
;; ADDITIONAL SECTION:
ns.myownserver.com. 38400 IN A 74.44.441.1
ns2.myownserver.com. 38400 IN A 74.44.441.254
ns3.myownserver.com. 38400 IN A 62.44.441.1
;; Query time: 3 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Oct 26 05:24:24 2007
;; MSG SIZE rcvd: 143
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(Your server answered ONLY A DOMAIN it is in charge of)
Done! Whew Go have a DrPepper or Mtn Dew or Cup of java.<br><br>Post edited by: BurtAdjoodani, at: 2007/10/26 01:41
