Enterprise Service Technologies (EST) in Computing and Telecommunications Services maintains a set of officially supported Domain Name System (DNS) servers for use by members of the K-State computing community.
EST is the primary contact for setting up and managing the central domain name service on campus. This includes new registrations, renewals and IP changes to current domains.
To initiate a change or addition to a current domain, send e-mail to dns@k-state.edu with the information request.
To initiate a request to purchase a domain, send e-mail to dns@k-state.edu. The following information is requested:
For complete information concerning the policy and procedures for domain registrations, please see the policy Registering Internet domain names at Kansas State University.
DNS servers are used to convert "Fully Qualified Domain Names" (FQDN) such as "www.ksu.edu" or "www.k-state.edu" into numeric IP addresses such as "129.130.12.1". This is necessary before a network connection can be made to the remote service or host. Since it is the DNS servers that provide this service, you must configure your system with the numeric IP addresses of the DNS servers. This is not usually necessary for other services such as SMTP or POP.
The DNS servers are located on a dedicated network that is directly connected to the network backbone.
The K-State DNS servers are for use by anyone on the K-State network.
If you are connected from the residence halls, elsewhere on campus, or via the K-State dial-in service, you should use K-State's DNS servers.
If you connect to the Internet by any other method, contact your Internet service provider for the appropriate DNS setup information. For security and performance reasons, the K-State DNS servers are configured to deny service to clients outside the K-State network.
The numeric IP addresses of the DNS servers are
In addition, we provide one server that is on a different subnet as a backup:
You should list these servers in a random order in your network-connection software to help distribute the load. The backup address should be listed last.
The following order of servers would be reasonable:
This configuration lists the primary DNS servers in a random order, but also includes the backup DNS server in the unlikely event that the subnet containing the primary DNS servers is unavailable.