11-08-2015
Quote:
Originally Posted by
cjcox
Think of nameservers as something different (but not necessarily) from your domain.
It's the DNS that holds the zone data for your somedomain.com. To make that official as far as the Internet goes that's why they are asking where your records go... that is what nameservers house the records.
Anymore unless the company is sizable, I chose to use a world wide redundant DNS service (multiple DNS servers with redundance) to house records for a domain (e.g. DNSMadeEasy for example). But as I alluded to earlier you can certainly host your own DNS server(s) (they like for you to have more than one if possible).
When DNS queries are made, ulimately thigns work from the root server down to the tld's etc... and along those paths, your case .com knows who (what DNS servers) stands authoritative for somedomain.com.
With that said, you or anyone else can choose to point to a DNS that "says" it stands authoritative for records for whoever (somedomain.com, mil.gov, etc)... if if that is your DNS that your pointing to you'll get back whatever name to IP (etc) that you have defined there.
Hope that wasn't too confusing.
Maybe another example. The Whitepages is a phone book. I could print my own phone book and change anyone's phone number I want. But this doesn't work at large because chances are people are using the official whitepages and not my hacked up copy.
Hello,
this still looks confusing to me.
you mean to say the domain registrar will put the somedomain.com in the rootservers , so then it becomes official ?
i was thinking about the whois server.
does it play a role in making the domain official ?
am trying to visualize another thing:
for example, if we query the A records of a domain , the query would also do a whois to find what are the official nameservers. the whois records would then be updated by the domain registrar.
please let me have your views. thanks.
9 More Discussions You Might Find Interesting
1. AIX
My only question is Can we have two auteritative Name servers for a single domain? Just a question. (1 Reply)
Discussion started by: vjm
1 Replies
2. Solaris
hi gurus,
need to check other than the hosts file, what else i need to change after we have changed the domain name in our company. currently, we are using olddnsname.com and will change it to newdnsname.com. i am not sure where else in solaris i need to take a look.
please advise.
thank... (4 Replies)
Discussion started by: kim_custodio
4 Replies
3. IP Networking
Hello,
I'm using CentOS 5.3, and I connect to a VPN in order to work. The problem is that I'm constantly accessing things on the local network and the remote network. But once I'm connected to the VPN I can't access local addresses by name, I have to use the ip-address.
What I'd like is to... (4 Replies)
Discussion started by: martincastell
4 Replies
4. Linux
Hi everybody,
for revolving local host name of my network, I set up an dns server to solve my problem, but til now, nothing happen when I ping a hostname, but work on IP. Can you help me to correct the configuration. Here is all my settings:
Voici mes fichiers de configuration:
-... (2 Replies)
Discussion started by: beloge2002
2 Replies
5. UNIX and Linux Applications
Hi,
We've got a samba server running in our DMZ. Our users drag & drop files on it for vendors. Everything was working perfectly until the powers that be decided to build a trust between a couple of internal domains.
Samba is now querying each server in the trust. When a user browses... (5 Replies)
Discussion started by: mph
5 Replies
6. Red Hat
I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based.
I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies
7. Shell Programming and Scripting
Hello to all,
May you help saying me how to flush a specific domain in Linux SunOS5
I know the command rndc is to flush DNS cache, but I would like to know:
1- How to do a flush only on specific domain
2- How to see the content of DNS Resolver cache (similar to info given by IPCONFIG... (2 Replies)
Discussion started by: Ophiuchus
2 Replies
8. UNIX for Advanced & Expert Users
Hello,
Our organization is planning to move one domain from Dreamhost to Hubspot. Lets say, it is gem.xyxyxyxyx.com. Please note, website is not being migrated from one server to another, it is just hosting company.
Here is from our internal DNS master server -
# cat... (6 Replies)
Discussion started by: solaris_1977
6 Replies
9. UNIX for Beginners Questions & Answers
In my /etc/resolv.conf file there is domain name defined. But when I do nslookup the domain name is not appended. Why? (18 Replies)
Discussion started by: broy32000
18 Replies
dns(n) dns dns(n)
NAME
dns - Tcl Domain Name Service Client
SYNOPSIS
package require Tcl 8.2
package require dns ?1.0.1?
::dns::resolve query ?options?
::dns::configure ?options?
::dns::name token
::dns::address token
::dns::cname token
::dns::status token
::dns::error token
::dns::reset token
::dns::wait token
::dns::cleanup token
DESCRIPTION
The dns package provides a Tcl only Domain Name Service client. You should refer to RFC 1034 and RFC 1035 for information about the DNS
protocol or read resolver(3) to find out how the C library resolves domain names. The intention of this package is to insulate Tcl scripts
from problems with using the system library resolver for slow name servers. It may or may not be of practical use. The package also
extends the package uri to support DNS URIs or the form dns:what.host.com or dns://my.nameserver/what.host.com. The dns::resolve command
can handle DNS URIs or simple domain names as a query.
Note: This package uses TCP to query DNS servers as the tcl core does not implement UDP networking. This means that this module will not
work if DNS over TCP is blocked by a firewall, or not accepted by the chosen nameserver.
COMMANDS
::dns::resolve query ?options?
Resolve a domain name using the DNS protocol. query is the domain name to be lookup up. This should be either a fully qualified
domain name or a DNS URI.
-nameserver hostname or -server hostname
Specify an alternative name server for this request.
-protocol tcp|udp
Specify the network protocol to use for this request. Can be one of tcp or udp. However only tcp is currently implemented in
the package.
-port portnum
Specify an alternative port.
-search domainlist
-timeout milliseconds
Override the default timeout.
-type TYPE
Specify the type of DNS record you are interested in. Valid values are A, NS, MD MF, CNAME, SOA, MB, MG, MR, NULL, WKS, PTR,
HINFO, MINFO, MX, TXT, AXFR, MAILB, MAILA and *. See RFC1035 for details about the return values.
-class CLASS
Specify the class of domain name. This is usually IN but may be one of IN for internet domain names, CS, CH, HS or * for any
class.
-recurse boolean
Set to false if you do not want the name server to recursively act upon your request. Normally set to true.
-command procname
Set a procedure to be called upon request completion. The procedure will be passed the token as its only argument.
::dns::configure ?options?
The ::dns::configure command is used to setup the dns package. The server to query, the protocol and domain search path are all set
via this command. If no arguments are provided then a list of all the current settings is returned. If only one argument then it
must the the name of an option and the value for that option is returned.
-nameserver hostname
Set the default name server to be used by all queries. The default is localhost.
-protocol tcp|udp
Set the default network protocol to be used. Defaults to tcp.
-port portnum
Set the default port to use on the name server. The default is 53.
-search domainlist
Set the domain search list. This is currently not used.
-timeout milliseconds
Set the default timeout value for DNS lookups. Defaults to 30 seconds.
::dns::name token
Returns a list of all domain names returned as an answer to your query.
::dns::address token
Returns a list of the address records that match your query.
::dns::cname token
Returns a list of canonical names (usually just one) matching your query.
::dns::status token
Returns the status flag. For a successfully completed query this will be ok. May be error or timeout or eof. See also ::dns::error
::dns::error token
Returns the error message provided for requests whose status is error. If there is no error message then an empty string is
returned.
::dns::reset token
Reset or cancel a DNS query.
::dns::wait token
Wait for a DNS query to complete and return the status upon completion.
::dns::cleanup token
Remove all state variables associated with the request.
EXAMPLES
% set tok [dns::resolve www.tcl.tk]
::dns::1
% dns::status $tok
ok
% dns::address $tok
199.175.6.239
% dns::name $tok
www.tcl.tk
Using DNS URIs as queries:
% set tok [dns::resolve "dns:tcl.tk;type=MX"]
% set tok [dns::resolve "dns://l.root-servers.net/www.tcl.tk"]
SEE ALSO
resolver(5)
AUTHORS
Pat Thoyts
KEYWORDS
DNS, resolver, domain name service
dns 1.0.1 dns(n)