what is the difference between public IP and  DNS server?
90386
A public IP address is an external address that someone can use to access a website or system outside of an internal LAN environment.  A DNS server translates a domain name into an IP address.  For example, when you type in the address http://answers.yahoo.com, a DNS server translates that into the IP address 209.191.70.167.
842143
http://www.publicproxyservers.com/page1.html  They are public proxy servers. You may also want to check out http://www.torrify.com/
186207
Internet Protocol address) The address of a device attached to an IP network (TCP/IP network). Every client, server and network device must have a unique IP address for each network connection (network interface). Every IP packet contains a source IP address and a destination IP address.\n\nStatic and Dynamic IP\n\nAn IP network is somewhat similar to the telephone network in that you have to have the phone number to reach a destination. The big difference is that IP addresses are often temporary.\n\nEach device in an IP network is either assigned a permanent address (static IP) by the network administrator or is assigned a temporary address (dynamic IP) via DHCP software. Routers, firewalls and proxy servers use static addresses as do most servers and printers that serve multiple users. Client machines may use static or dynamic IP addresses. The IP address assigned to your service by your cable or DSL Internet provider is typically dynamic IP. In routers and operating systems, the default configuration for clients is dynamic IP (see DHCP).\n\nDotted Decimals\n\nIP addresses are written in "dotted decimal" notation, which is four sets of numbers separated by periods; for example, 204.171.64.2. If you knew the IP address of a Web site, you could enter the dotted decimal number into your browser instead of the domain name (which is why we have DNS!).\n\nAlthough the next version of the IP protocol offers a virtually unlimited number of unique addresses (see IPv6), the traditional IP address (IPv4) uses a 32-bit number that defines both the network and the host computer. The network class determines how many of the 32 bits are used for the network address, leaving the remaining bits for use as the host number (note the numbers of networks and hosts in the table below). The host number can be further divided between subnetworks and hosts
539213
IMO it's the DNS server [which translates names into ip numbers]. Call your ISP - it may be their problem, not yours.
142452
1. The difference between NAT, public, and private addresses. First public addresses. These are addresses by which others on the internet can refer to you. Another way to think of it is these are the addresses that are visible to people outside your LAN. Private addresses are just the opposite. These are the addresses that are used on your local network and they are not used outside the LAN. Thus if you encounter internet traffic from an address like 10.1.1.5, you can safely disregard it. NAT, or Network Address Translation, is done at your firewall or gateway and it essentially translates your private address into a public address. For example, your local network may be using addresses in the 192.168.1.0-254 range. These are private addresses and cannot be used on the internet. When you try to access the internet, your firewall or gateway translates that address to your public address. Thus, if you have a very simple network with only one public IP address, you could have, say, 10 clients on your internal network, but when they access the internet, they all appear to come from your single public address. Then there is static NAT (SNAT) and dynamic NAT (DNAT), but that's a little outside the scope of your question. \n2. Where to enter the public address. When you say that you have one of the clients acting like a sever, I assume you mean that it is functioning as the firewall/gateway? If that is the case, this is the only box on which you need to have the public IP address. This is for your outside-facing interface, and your private address will be on your inside-facing interface. Your other client machines don't have any need or use for the public IP address.
1038354
Just install IIS or use Apache - setup the website on any port (most likely port 80 if you don't want to type the port in).  Hook up to  your router (usually 192.168.0.1) and use port forwarding and choose whatever port above and point it to your internal IP of your server.\n\nIf you want to have a domain, just setup one with DNS2GO which will automatically configure a dynamic IP.  GOOD LUCK!
24316
Nameservers, or DNS Servers, are servers that provide mapping between internet names (like "answers.yahoo.com") and IP addresses (like "209.191.70.167").  They are essential for the operation of the internet as we know it.  Without name servers, you would have to know the IP address of every website you wanted to browse or every mail server you wanted send mail to or through.\n\nThere are a variety of name records that are stored on a DNS server.  They include:\n\nSOA -- Start of Authority records that tell you information about how to reach a domain's servers and owner\n\nA -- Address records that do a direct map of name to address\n\nCNAME -- Alias records that tell you that, for example, "Answers.yahoo.com" really means you need to look up "web-vip1.search.mud.yahoo.com".\n\nPTR -- Reverse address records that tell you what name is associated with a specific address.\n\nAnd, the one you asked about:\n\nMX -- Mail Exchanger records.  MX records tell you, in order, which mail server handles inbound e-mail for a specific domain.  When you send e-mail to, for example, bgates@microsoft.com, your mail server checks the mx records for microsoft.com.  Starting with the one that has the lowest priority number, it tries to deliver the e-mail to that box.  If that box is down, or it gets back a non-fatal error message, then it moves to the box with the next highest priority number.\n\nThe sources will tell you MUCH more information.
60381
Both answers above are true, but are limited.\n\nYes, in most cases you need a static IP, but this is not always the case.  There are services such as No-IP.com that will allow you to link a domain name to a dynamic IP, as long as you're running their client on your server.\n\nPlease note that most ISPs do not allow public access web servers from personal computers, regardless of if you have a static or dynamic IP.  Check with your ISP before setting up your server for public access.\n\nAs far as servers go, IIS is one option, but there are other alternatives, one of which is Apache.  Apache is free, supports multiple platforms (it can run on inux, MACs, and Windows), and can run a host of different modules including PHP, Perl, MySQL, and more.  One easy to set up version can be found on Apache Friends.\n\nAlso, you should only need to configure one of three ports (80, 8000, or 8080) to be open on your firewall in order for your server to work.  Just be sure to configure your web server to "listen" to teh port you assign open.
354148
It's generally not possible to get the IP address of a computer that is behind a NAT firewall.  It would be rather useless anyway as you could easily have many sessions coming in through NAT'd connections that have the same IP address.  For session control, you'd be far better off using a session cookie.
167559
do you mean domain name server???\n\nIt resolves IP addresses to alphanemeric names
351709
Phew, weighty questions there. Well, a DNS is a "Domain Name Server" Essentially what it does is translate a website's name (ie www.yahoo.com) into it's ip address so that the server can be found. The internet isn't built on words, it's built on numbers, so somewhere along the line, in order for a computer hosting a website to be found, some other computer has to know that www.yahoo.com is hosted on 192.0.0.1 or some such thing. The DNS server is the computer that knows. \n\nNow a proxy server is simply a computer that fetches the internet for you, instead of you going directly to it. If you're not using a proxy, you type in www.yahoo.com, it goes to the dns server, which finds the site, and yahoo sends it's webpage to your computer. If you *are* using a proxy, you type in www.yahoo.com, it goes to the proxy server, then to the dns, then yahoo sends it's page to the proxy, which sends it on to your pc. Yahoo doesn't know you're browsing their site, they only know the proxy is. It's like... sending out a friend to buy some embarrassing personal item from the store. Instead of you going yourself, you give them the money, they go, get the item and bring it back to you, and no one at the store knows you have foot fungus, they think your friend does. Get it?\n\nAs for the last part... I'm really don't know what you're asking, there, sorry.
1178539
No is not even numbers. It can be anything with in (01-255)\nThere are 2 types of IPS\n1. Dynamic ( It changes every time u connect)\n2. Static ( It remains the same all the time)\n\nThe IP types are controlled by the Server.\n\n\nNeo\n\nNeo
335729
You can use a NAT server to share the static IP address.
673697
if you try to ping the domain name im assuming that you are unable to resolve the host name.  If this is happening make sure in TCP/IP properties that you have the DNS Server Addresses right (or in your dhcp setup... whatever provides your network info)  If that is set up correctly make sure that DNS is running on your server (that the service is started)  If that is fine I would assume that your DNS is setup Incorrectly.  You might want to try to get a basic setup of dns on it to test it.  Its hard to give steps with out knowing more details (type of server, Network layout, type of workstation, Linux, Unix, Mac, Window, Dhcp, static IP address)
573628
your dns cache is stored by windows, as are cookies. you can adjust cookies settings by going to tools > internet options > privacy\nand adjust it from there.\nDNS chache settings can be adjusted through the registry, but most end users do not need to change this, and shouldn't for various reasons\nand no, DNS servers do not store your cookies
1056432
The DHCP server at your ISP generates the IP address.  You are typing the correct commands to release/renew your IP address.  The IP address they issue is within a range of addresses on the network they have registered to be able to use.  You'll have to switch ISP's if you want to be on another network.
82485
IP's are assigned to clients by a service known as DNS (Domain Name Service), your ISP has a DNS client that connects to the closest DNS on its route to query for a free (re-usable, of course!) IP. when it finds one, it assigns it to you, and registers that IP with the DNS (so it is not 're-assigned' while you are using it!).\nThere are only 7 DNS in the whole world, and they manage to keep up the traffic of the whole internet, pheew, think about that hardware, sweet God!!!\n\nMoreover, IP's refer to a 'domain name'. right, the numbers encrypt an actual name. like, www.yahoo.com = xxx.XXX.xx.XXX . Thus, if you want your computer to have always a same 'domain name', you need a "static IP", something you have to pay the DNS services a lot of money for...