PHNET DNS Hosting Service
; Note that all names in this page are terminated with a period.
; This is not an accident. Names which are not terminated with a period
; would automatically get your domain name appended to them.
; In this example, the DNS record "server IN A 188.8.131.52" would be saved
; by our system as "server.myschool.edu.ph. IN A 184.108.40.206"
; We now begin with the DNS record examples.
; The "A" record is an "address" record. It assigns an IP address
; to a given hostname. The IP addresses used in this example
; are not valid. Be sure that you use your correct addresses.
myschool.edu.ph. IN A 220.127.116.11
mail.myschool.edu.ph. IN A 18.104.22.168
mail2.myschool.edu.ph. IN A 22.214.171.124
; The following lines are examples of Mail Exchanger (MX) records.
; The MX record tells Internet servers to deliver e-mail
; to particular hosts. These hosts are known as the Mail Exchangers
; for the domain myschool.edu.ph. You have to make sure that the
; hosts have a properly configured mail server software (e.g. Sendmail
; from www.sendmail.org is free) to receive the e-mail.
; 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
; @myschool.edu.ph 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 this example, mail.myschool.edu.ph would be the first to
; be contacted for email delivery. If that fails, email would be
; delivered to mail2.myschool.edu.ph.
myschool.edu.ph. IN MX 10 mail.myschool.edu.ph.
myschool.edu.ph. IN MX 20 mail2.myschool.edu.ph.
; 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. We have an example of a long TXT record below.
; The "CNAME" record states that the name on the left side is just
; an alias for the name on the right. That is, the real name
; or canonical name of the host on the left side is the name on the
; right side. Note that the right hand side 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 "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 uses a TXT record for its site verification. Google would
; ask that you create a specific TXT record which it could query
; and then verify. By being able to create the TXT record, you show
; 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 and would certainly not work for you.
myschool.edu.ph. IN TXT ("google-site-verification="
; A subdomain is a domain. It needs an authoritative DNS
; server just like any other domain. The "NS" record sets
; the authoritative Domain Name Server for a domain. For the
; PHNET DNS Hosting Service, there should be no "NS" records
; EXCEPT if a subdomain is to be defined.
; If you plan to use gabriela.ph.net and gomez.ph.net as the
; authoritative DNS servers for your subdomain, then 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
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
; it may be used in a SRV record.
_sip._tcp.myschool.edu.ph. IN SRV 10 25 5060 voip.myschool.edu.ph.
; Nothing follows