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
LEARN ABOUT OSX
net::dns::resolver::programmable
Net::DNS::Resolver::Programmable(3) User Contributed Perl Documentation Net::DNS::Resolver::Programmable(3)
NAME
Net::DNS::Resolver::Programmable - programmable DNS resolver class for offline emulation of DNS
VERSION
0.003
SYNOPSIS
use Net::DNS::Resolver::Programmable;
use Net::DNS::RR;
my $resolver = Net::DNS::Resolver::Programmable->new(
records => {
'example.com' => [
Net::DNS::RR->new('example.com. NS ns.example.org.'),
Net::DNS::RR->new('example.com. A 192.168.0.1')
],
'ns.example.org' => [
Net::DNS::RR->new('ns.example.org. A 192.168.1.1')
]
},
resolver_code => sub {
my ($domain, $rr_type, $class) = @_;
...
return ($result, $aa, @rrs);
}
);
DESCRIPTION
Net::DNS::Resolver::Programmable is a Net::DNS::Resolver descendant class that allows a virtual DNS to be emulated instead of querying the
real DNS. A set of static DNS records may be supplied, or arbitrary code may be specified as a means for retrieving DNS records, or even
generating them on the fly.
Constructor
The following constructor is provided:
new(%options): returns Net::DNS::Resolver::Programmable
Creates a new programmed DNS resolver object.
%options is a list of key/value pairs representing any of the following options:
records
A reference to a hash of arrays containing a static set of Net::DNS::RR objects. The hash entries must be indexed by fully
qualified domain names (lower-case, without any trailing dots), and the entries themselves must be arrays of the RR objects
pertaining to these domain names. For example:
records => {
'example.com' => [
Net::DNS::RR->new('example.com. NS ns.example.org.'),
Net::DNS::RR->new('example.com. A 192.168.0.1')
],
'www.example.com' => [
Net::DNS::RR->new('www.example.com. A 192.168.0.2')
],
'ns.example.org' => [
Net::DNS::RR->new('ns.example.org. A 192.168.1.1')
]
}
If this option is specified, the resolver retrieves requested RRs from this data structure.
resolver_code
A code reference used as a call-back for dynamically retrieving requested RRs.
The code must take the following query parameters as arguments: the domain, RR type, and class.
It must return a list composed of: the response's RCODE (by name, as returned by Net::DNS::Header->rcode), the "aa" (authoritative
answer) flag (boolean, use undef if you don't care), and the Net::DNS::RR answer objects. If an error string is returned instead
of a valid RCODE, a Net::DNS::Packet object is not constructed but an error condition for the resolver is signaled instead.
For example:
resolver_code => sub {
my ($domain, $rr_type, $class) = @_;
...
return ($result, $aa, @rrs);
}
If both this and the "records" option are specified, then statically programmed records are used in addition to any that are
returned by the configured resolver code.
defnames
dnsrch
domain
searchlist
debug
These Net::DNS::Resolver options are also meaningful with Net::DNS::Resolver::Programmable. See Net::DNS::Resolver for their
descriptions.
Instance methods
The following instance methods of Net::DNS::Resolver are also supported by Net::DNS::Resolver::Programmable:
search: returns Net::DNS::Packet
query: returns Net::DNS::Packet
send: returns Net::DNS::Packet
Performs an offline DNS query, using the statically programmed DNS RRs and/or the configured dynamic resolver code. See the "new"
constructor's "records" and "resolver_code" options. See the descriptions of search, query, and send for details about the calling
syntax of these methods.
print
string: returns string
searchlist: returns list of string
defnames: returns boolean
dnsrch: returns boolean
debug: returns boolean
errorstring: returns string
answerfrom: returns string
answersize: returns integer
See "METHODS" in Net::DNS::Resolver.
Currently the following methods of Net::DNS::Resolver are not supported: axfr, axfr_start, axfr_next, nameservers, port, srcport, srcaddr,
bgsend, bgread, bgisready, tsig, retrans, retry, recurse, usevc, tcp_timeout, udp_timeout, persistent_tcp, persistent_udp, igntc, dnssec,
cdflag, udppacketsize. The effects of using these on Net::DNS::Resolver::Programmable objects are undefined.
SEE ALSO
Net::DNS::Resolver
For availability, support, and license information, see the README file included with Net::DNS::Resolver::Programmable.
AUTHORS
Julian Mehnle <julian@mehnle.net>
perl v5.16.2 2013-08-25 Net::DNS::Resolver::Programmable(3)