DNS
Readme has moved online to http://www.ritlabs.com/tinyweb/
tangcheungwang
69.109.168.118
Your username is "Dennis36".
Your temporary password is " ".
"tangcheungwang.com" site is live
Nameserver 1: ns2.zoneedit.com (69.72.158.226)
Nameserver 2: ns17.zoneedit.com (209.126.159.118)
How can I check to see if DNS is working?
A frequent mistake is to use "ping" to test DNS. On Windows NT/2K and Unix,
there are tools
called "nslookup" and "dig".
- Before you contact ZoneEdit, you can check to see whether or not your
registrar is
pointing your domain to the correct nameservers. The "whois" information is
often wrong, and
should not be used. Go to a command prompt/console and enter the command:
nslookup -type=NS yourdomainname.com
If the response does not contain all of the correct name servers, then you
should contact
your registrar and have them fix it.
- To check to see whether a particular server is responding, you can add the
server name:
nslookup www.yourdomainname.com ns1.zoneedit.com
If the response has a bunch of 'root-servers' that means the server does not
know about the
domain name and is referring you elsewhere.
- To look for a certain record type, like the "MX" record or the "SOA" record,
you can use
the parameter "-type=MX" or "-type=SOA".
nslookup -type=MX yourdomainname.com
- If you don't have access to "nslookup" or "dig", you can use our online DNS
lookup tool
instead. It works for all domain names - not just zoneedit ones.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\熊ビル>nslookup -type=NS tangcheungwang.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
*** UnKnown can't find tangcheungwang.com: Non-existent domain
C:\Documents and Settings\熊ビル>nslookup -type=NS buysomemilk.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
Non-authoritative answer:
buysomemilk.com nameserver = ns1.servage.net
buysomemilk.com nameserver = ns2.servage.net
buysomemilk.com nameserver = ns3.servage.net
buysomemilk.com nameserver = ns4.servage.net
ns1.servage.net internet address = 62.214.98.76
ns2.servage.net internet address = 62.214.98.80
ns3.servage.net internet address = 62.214.98.110
ns4.servage.net internet address = 62.214.98.71
C:\Documents and Settings\熊ビル>nslookup www.buysomemilk.com ns1.servage.net
*** Can't find server name for address 62.214.98.76: Non-existent domain
Server: UnKnown
Address: 62.214.98.76
Name: www.buysomemilk.com
Address: 62.214.98.34
C:\Documents and Settings\熊ビル>nslookup -type=MX buysomemilk.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
Non-authoritative answer:
buysomemilk.com MX preference = 20, mail exchanger = mail2.servage.net
buysomemilk.com MX preference = 10, mail exchanger = mail1.servage.net
buysomemilk.com nameserver = ns2.servage.net
buysomemilk.com nameserver = ns3.servage.net
buysomemilk.com nameserver = ns4.servage.net
buysomemilk.com nameserver = ns1.servage.net
mail1.servage.net internet address = 62.214.98.110
mail2.servage.net internet address = 62.214.98.110
ns1.servage.net internet address = 62.214.98.76
ns2.servage.net internet address = 62.214.98.80
ns3.servage.net internet address = 62.214.98.110
ns4.servage.net internet address = 62.214.98.71
C:\Documents and Settings\熊ビル>nslookup -type=SOA buysomemilk.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
Non-authoritative answer:
buysomemilk.com
primary name server = ns1.servage.net
responsible mail addr = hostmaster.servage.com
serial = 200509177
refresh = 21600 (6 hours)
retry = 3600 (1 hour)
expire = 1209600 (14 days)
default TTL = 172800 (2 days)
buysomemilk.com nameserver = ns4.servage.net
buysomemilk.com nameserver = ns1.servage.net
buysomemilk.com nameserver = ns2.servage.net
buysomemilk.com nameserver = ns3.servage.net
ns1.servage.net internet address = 62.214.98.76
ns2.servage.net internet address = 62.214.98.80
ns3.servage.net internet address = 62.214.98.110
ns4.servage.net internet address = 62.214.98.71
C:\Documents and Settings\熊ビル>
http://www.zoneedit.com/doc/faq.html#pricing
- How can I check to see if DNS is working?
A frequent mistake is to use "ping" to test DNS. On Windows
NT/2K and Unix, there are tools called
"nslookup"
and "dig".
- Before you contact ZoneEdit, you can check to see
whether or not your registrar is pointing your domain to the
correct nameservers. The "whois" information is often wrong,
and should not be used. Go to a command prompt/console and
enter the command:
nslookup -type=NS yourdomainname.com
If the response does not contain all of the correct name
servers, then you should contact your registrar and have
them fix it.
- To check to see whether a particular server is
responding, you can add the server name:
nslookup www.yourdomainname.com
ns1.zoneedit.com
If the response has a bunch of 'root-servers' that means the
server does not know about the domain name and is referring
you elsewhere.
- To look for a certain record type, like the "MX" record
or the "SOA" record, you can use the parameter "-type=MX" or
"-type=SOA".
nslookup -type=MX yourdomainname.com
- If you don't have access to "nslookup" or "dig", you
can use our
online DNS lookup tool instead. It works for all domain
names - not just zoneedit ones.
|
|
- If you want to back up all ZoneEdit DNS data for a given
zone, use named-xfer:
named-xfer -z atreju.com -f atreju.com.txt
ns1.zoneedit.com.
|
|
What is an "A" record?
An "A" record, also called an "address" record, ties a domain name to an IP
address. If there is a server on the Internet that is configured to handle
traffic for this domain, you can enter the name of the domain (like "www.ZoneEdit.com")
and the IP address of the server (like "209.81.71.236"), and almost immediately,
anyone surfing to that domain connects to the correct server.
What is an "MX" record?
"MX" ("Mail eXchanger") records are used to specify what server on the Internet
is running e-mail software that is configured to handle e-mail for your domain.
If you want your ISP to handle routing the e-mail for your domain to you, you
need to specify the domain name or IP address of your ISP's mail server. In
addition, you can specify the rank of each mail server when you have more than
one. Make sure your ISP knows that you're using their servers to route your
domain's email, or all your e-mail will "return to sender"!
If you want to use our servers instead of your ISP's, don't specify any "MX"
records, just configure our simple MailForward service!
What is a "CNAME" record?
"CNAME" records, short for "Canonical Name", create an alias from a domain name
to another. You could create an alias from "yahoo.mydomain.com" to "www.yahoo.com",
and every reference to "yahoo.mydomain.com" would go to the other location,
regardless how yahoo changed their IP addresses! Be careful, however; CNAMEs
won't work everywhere. If you create an MX record, and the name used for the
mail server was defined using a CNAME, you might lose e-mail!
|