Sponsored Content
Top Forums Web Development (WHM) Primary Resolver and Nameserver confusion Post 302838413 by Astrocloud on Monday 29th of July 2013 02:43:57 PM
Old 07-29-2013
Question (WHM) Primary Resolver and Nameserver confusion

Okay,

I know generally how the internet works but here I am confused. Every website that I've worked on prior to this had a vendor providing Nameserver services -Meaning that I just pointed my DNS to their server and they do the rest.

Now, I am confused by what the Primary Resolver is supposed to point to. I am supposed to use WHM as a private nameserver but then does the Primary resolver point to itself? That doesn't seem right. Do I have to set this up? Can I remove it?

Say for example I have a website named: FatUnixGuy.com and I have two fixed IP addresses reserved for this at 192.168.22.10 and 192.168.22.11
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

need advice on nameserver configuration

on a Red Hat server I am running name server (ns1.mynameserver.com , ns2.mynameserver.com) can anybody advice how to set my server so that it automatically forwards domains that have ns1.mynameserver.com , ns2.mynameserver.com as nameserver address to a specific url/page, without actually adding... (0 Replies)
Discussion started by: wanex
0 Replies

2. UNIX for Dummies Questions & Answers

nslookup *** Can't initialize resolver

Has anyone seen this message before? I have a DNS problem. Recently DNS has been moved to two new servers, which I can ping. I changed the /etc/resolv.conf to point to these boxes but now I get the *** Can't initialize resolver message. Any ideas? (2 Replies)
Discussion started by: korfnz
2 Replies

3. UNIX and Linux Applications

BIND (Name Server & Resolver)

Hi, i'm looking information about how BIND (Name Server & Resolver) works... And how Server/Client communicates... I found a lot of information of what BIND is and how to configure it, but nothing about how it works, does anybody know where i can found something useful?? I don't need code, just... (3 Replies)
Discussion started by: Sandia_man
3 Replies

4. Red Hat

two dns search with 4 nameserver

Hi all, Does someone use this kind of config on /etc/resolv.conf? search domain1.com domain2.com nameserver 1.x.x.x nameserver 2.x.x.x nameserver 3.x.x.x nameserver 4.x.x.x Is that going to work properly? I heard that only 3 lines are enabled on resolv.conf. Is that true? Thanks! (1 Reply)
Discussion started by: itik
1 Replies

5. UNIX for Dummies Questions & Answers

NameServer not accessible

Hi everybody I am facing a little problem with names servers. I have a VPS with Kloxo installed on it I have registered 2 name servers (i.e. ns1.domain.com and ns2.domain.com) past one month. These nameservers are not accessible yet. I have check the nameserver on internic site and they are... (3 Replies)
Discussion started by: rizwan65
3 Replies

6. HP-UX

Which nameserver is used?

Hello, i change the nameserver in the resolv.conf file and want to test the new settings. On Linux i can call nslookup and it shows the nameserver which is used: ># nslookup www.unix.com Server: XXX.XXX.XXX.XXX Address: XXX.XXX.XXX.XXX#53 Non-authoritative answer:... (3 Replies)
Discussion started by: soeren1176
3 Replies

7. Shell Programming and Scripting

WHM Crontab and Folder Renaming to current date

Hello, i am trying to rename a folder named 'cpbackup' to current date in our WHM Root via setting up a cronetab entry. but the folder does not get renamed on the scheduled time :confused: */1 * * * * timestamp=$(date +%m%d%Y);/bin/mv /ac_backups/cpbackup /ac_backups/$timestamp (4 Replies)
Discussion started by: kandyjet
4 Replies

8. IP Networking

[Android-Networking] can't acces internet, while settings says all is ok => Routing/Nameserver prob

Hello, since a while, i have a very strange and frustrating network problem with my Huawei p6(Android 4.4.2). The ROM is "Omni Rom", i think - but it shouldn't matter. The problem is: when i try to connect through wlan (i have no mobile internet), according to the network manager of android,... (1 Reply)
Discussion started by: Palindrom
1 Replies

9. UNIX for Beginners Questions & Answers

Bind: Can you configure multiple domains using the same nameserver

Can you add multiple domains to a nameserver without creating a new IP address? I have one IP address on my machine and have configured forward and reverse zone files. Names are resolving fine. I know I can add another domain to the named.conf file and create new forward and reverse files. what... (2 Replies)
Discussion started by: LinuxGirl
2 Replies
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)
All times are GMT -4. The time now is 09:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy