PHNET

PHNET DNS Hosting Service


Sample DNS records for the domain myschool.edu.ph.



;        PRELIMINARY NOTES
;    These are DNS records for the fictitious domain
; myschool.edu.ph using fictitious IP addresses.
; A line which starts with a semicolon is a comment and is
; not considered as a DNS record.
;    If you wish to cut and paste this for your own records,
; just leave out all the comment lines and (1) replace "myschool.edu.ph"
; with your own domain and (2) replace the IP addresses with your
; IP addresses. Each record must be in one line.


;    Names which are not terminated with a period automatically
; get your domain name appended to them. This behavior allows you
; to type records without specifying your domain name.
; Examples:


server IN A 1.2.3.4
mail IN MX 5 google.com
x.myschool.edu.ph. IN A 5.6.7.8


; The above three DNS records would be saved by our system, respectively, as


server.myschool.edu.ph. IN A 1.2.3.4
mail.myschool.edu.ph. IN MX 5 google.com.myschool.edu.ph.
x.myschool.edu.ph. IN A 5.6.7.8


; If you do not want your domain name to be appended to your hostname, you must terminate
; the hostname with a period.


;      EXAMPLES OF DNS RECORDS


;    The Address (A) record assigns an IP address
; to a given hostname. The IP addresses used in this example
; are not valid. Be sure that you use your own correct IP addresses.


myschool.edu.ph. IN A 1.2.3.4
mail.myschool.edu.ph. IN A 4.5.6.7
mail2.myschool.edu.ph. IN A 8.9.10.11


;    The Canonical Name (CNAME) record states that the name on the
; left side is an alias for the name on the right. That is, the name
; on the right side is the canonical name of the name on the left side.
; The right hand side name must be defined before it can be
; used. Once an alias is defined, it can never be used on the left
; side of any record.


www.myschool.edu.ph. IN CNAME myschool.edu.ph.


;    The Mail Exchanger (MX) record declares that email
; addressed to a domain name (e.g. myschool.edu.ph) must be delivered
; to particular hosts known as the Mail Exchangers for the domain name.
;
;    You may have as many MX hosts for your domain as you like.
; The one with the lowest number has the highest precedence.
; Mail servers in the Internet will deliver e-mail for
; to the host with the highest precedence
; (i.e. lowest precedence number). When this host does not answer,
; mail will be delivered to the host with the next precedence level.
;
;    In the following example, we have two MX servers for the domain
; myschool.edu.ph. These two servers are the *ONLY* receivers for
; any email with a @myschool.edu.ph address.
; The MX host mail.myschool.edu.ph will be the first to be contacted.
; If it is not able to receive the email for any reason (e.g. it is
; unreachable), then the email would be delivered to the next
; MX server aspmx.l.google.com.


myschool.edu.ph. IN MX 10 mail.myschool.edu.ph.
myschool.edu.ph. IN MX 20 ASPMX.L.GOOGLE.COM.


;    Some institutions use Google's G-Suite system. To verify domain name
; ownership, Google would ask that you create a special MX record
; with a very long name. Unfortunately, the name is often too long
; and extends beyond one line-- unacceptable to our system. You should
; contact Google and ask for a TXT record verification code instead of using
; the MX verification code.


;    The Text (TXT) record is used to hold any descriptive data.


myschool.edu.ph. IN TXT "The Best School in the World"


;    If you have a very long description, you may break it up
; into different lines by enclosing the entire string within
; parentheses. This is the only exception to the "one record,
; one line" rule.
;    Google can use a TXT record for its site verification. Google will
; ask that you create a specific TXT record which it could query
; and then verify. By creating the TXT record, you prove to Google
; that you have control of the domain. Below is an example of a long
; TXT record used for Google site verification. The code, of course, is
; fictitious. You must request Google for your own code.


myschool.edu.ph. IN TXT ("google-site-verification="
"Fe8gEezFhm8hUfrEIry-"
"mcRqz3Zg-Ew9F6HnzhIg69Yo"
"asdkjad91231kjkjasdaslkl")


;    The Name Server (NS) record sets the authoritative DNS
;server for a domain. The PHNET DNS Hosting Service automatically
;creates the necessary NS records for your domain. The ONLY
;time you need to create this record is when you want to create
;a subdomain. For the PHNET DNS Hosting Service, there should
;be no NS records except if a subdomain is to be defined.
;Furthermore, if you plan to use gabriela.ph.net and gomez.ph.net
; as the authoritative DNS servers for your subdomain, you would
; have to register this subdomain for the PHNET DNS Hosting
; Service as well.
;    In this example, the school is creating a subdomain for its
; Cagayan De Oro campus which it wishes to name "cdo."
; The authoritative DNS server for this new domain is set to be
; server.example.com.


cdo.myschool.edu.ph. IN NS server.example.com.


;    The Service record (SRV) defines the location, i.e., the hostname
; and port number, of servers for specified services. This record is
; is most often used for the Session Initiation Protocol (SIP).
;
;    In this example, the school has a server named voip.myschool.edu.ph
; listening on TCP port 5060 for Session Initiation Protocol (SIP) protocol
; services. It has a priority of 10 and a weight of 25. The server
; voip.myschool.edu.ph. must already have a defined A record before it
; may be used in a SRV record.

_sip._tcp.myschool.edu.ph. IN SRV 10 25 5060 voip.myschool.edu.ph.


; This is the end of the DNS Record Examples. Nothing follows



Home  |  EDU.PH DNS  |  Services

Copyleft © 1993-2022, Some Rights Reserved.
Philippine Network Foundation, Inc.(PHNET)

2721 Berkeley Residences
Katipunan Avenue corner Escaler Street,
Loyola Heights,Quezon City
PHILIPPINES

Telefax : +63 2 7621-2437