Sponsored Content
Top Forums UNIX for Advanced & Expert Users Different Nameservers for Different Domains? Post 302248424 by vertigo23 on Friday 17th of October 2008 03:23:57 PM
Old 10-17-2008
Actually, that should do the trick nicely - adding a forwarding zone for the external DNS. Thanks for the pointer!
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

multiple domains

Hello, I have 3 domains virtually hosted "name based" the first one "domain1.com" has its ServerName entered as domain1.com. this domain will load in a browser by www.domain1.com or simply domain1.com. the next two domains "domain2.com" and "domain3.com" ServerNames are listed as domain2.com and... (2 Replies)
Discussion started by: ericg
2 Replies

2. UNIX for Advanced & Expert Users

best solution for managing many nameservers

Hello, i was searching around for good solution for managing many nameservers to add the records on the slave servers and update them and if possible some web-based manegment for non-experianced customers. anyone has an idea where can i find such solution? (1 Reply)
Discussion started by: Bashar
1 Replies

3. UNIX for Dummies Questions & Answers

blocking domains

Dear All , Kindly note I have sun solaries 7 . I want to block a domain who keep sending emails to my domain and users . thanks (1 Reply)
Discussion started by: tamemi
1 Replies

4. News, Links, Events and Announcements

Verisign and the .com and .net domains

You probably have heard about Verisign's recent controversial action. If not, here is one link. I hope that you also know that the latest version of BIND has been released and it includes the ability to reject undelegated responses from top level domains except for a few that you can... (3 Replies)
Discussion started by: Perderabo
3 Replies

5. UNIX for Dummies Questions & Answers

creating domains

ok i am setting up dns or going to do it with solaris 9 once u setup the domain what file can u look @ to see if it setup or not (4 Replies)
Discussion started by: rmuhammad
4 Replies

6. Solaris

Dynamic System Domains

Hi, I've got to write "something" about how to build a dynamic domain on an M5000. simple question: anyone done anything like that? not really finding much by googling either. please share...:o (3 Replies)
Discussion started by: frustin
3 Replies

7. UNIX for Dummies Questions & Answers

Sub domains from report

Hi, I have a report containing severals organization's email address. The address contain several sub domains, and i need to pull those out. mail domain ( example.com) .................. The report column contain mail address in this format : john1@sub1.example.com... (2 Replies)
Discussion started by: john_prince
2 Replies

8. IP Networking

VLANs and their domains

Hey everyone. I work in a data center, and I'm working on getting my CCNA. Now when I read articles on the idea of VLAN's it makes sense. Especially if you have multiple switches daisy chained in multiple locations. My two main questions though are that most of these examples use PC's as examples... (2 Replies)
Discussion started by: Lost in Cyberia
2 Replies
Net::DNS::ZoneFile(3)					User Contributed Perl Documentation				     Net::DNS::ZoneFile(3)

NAME
Net::DNS::ZoneFile - DNS zone file SYNOPSIS
use Net::DNS::ZoneFile; $zonefile = new Net::DNS::ZoneFile( 'db.example' ); while ( $rr = $zonefile->read ) { $rr->print; } @zone = $zonefile->read; DESCRIPTION
Each Net::DNS::ZoneFile object instance represents a zone file together with any subordinate files nominated using $INCLUDE directives. Zone file syntax is defined by RFC1035. A program can have multiple zone file objects, each maintaining its own independent parser state information. The parser supports both the $TTL directive defined by RFC2308 and the BIND $GENERATE syntax extension. All RRs in a zone file must have the same class, which may be specified for the first RR encountered and is then propagated automatically to all subsequent records. METHODS
new $zonefile = new Net::DNS::ZoneFile( 'db.example', ['example.com'] ); Returns a Net::DNS::ZoneFile object which represents the zone file specified in the argument list. The file is opened for reading and remains open until exhausted or all references to the ZoneFile object cease to exist. The optional second argument specifies $ORIGIN for the zone file. read $rr = $zonefile->read; When invoked in scalar context, returns the next RR encountered in the zone file, or undefined if end of data has been reached. Comments and blank lines are silently disregarded. $INCLUDE, $ORIGIN, $TTL and $GENERATE directives are processed transparently. @rr = $zonefile->read; When invoked in list context, returns the list of all RR objects in the zone file. name $filename = $zonefile->name; Returns the name of the zone file from which RRs will be read. $INCLUDE directives will cause this to differ from the filename argument supplied when the object was created. line $line = $zonefile->line; Returns the line number of the last non-continuation line encountered in the current zone file. origin $origin = $zonefile->origin; Returns the fully qualified name of the current origin within the zone file. ttl $ttl = $zonefile->ttl; Returns the default TTL as specified by the $TTL directive. COMPATIBILITY WITH Net::DNS::ZoneFile 1.04 Applications which depended on the Net::DNS::ZoneFile 1.04 package will continue to operate with minimal change using compatibility interface described below. use Net::DNS::ZoneFile; $listref = Net::DNS::ZoneFile->read( $filename, $include_dir ); $listref = Net::DNS::ZoneFile->readfh( $handle, $include_dir ); $listref = Net::DNS::ZoneFile->parse( $string, $include_dir ); $listref = Net::DNS::ZoneFile->parse( $string, $include_dir ); $_->print for @$listref; The optional second argument specifies the default path for filenames. The current working directory is used by default. Although not available in the original implementation, the RR list can be obtained directly by calling in list context. @rr = Net::DNS::ZoneFile->read( $filename, $include_dir ); read $listref = Net::DNS::ZoneFile->read( $filename, $include_dir ); read() parses the specified zone file and returns a reference to the list of Net::DNS::RR objects representing the RRs in the file. The return value is undefined if the zone data can not be parsed. readfh $listref = Net::DNS::ZoneFile->readfh( $handle, $include_dir ); read() parses data from the specified file handle and returns a reference to the list of Net::DNS::RR objects representing the RRs in the file. The return value is undefined if the zone data can not be parsed. parse $listref = Net::DNS::ZoneFile->parse( $string, $include_dir ); $listref = Net::DNS::ZoneFile->parse( $string, $include_dir ); parse() interprets the argument string and returns a reference to the list of Net::DNS::RR objects representing the RRs. The return value is undefined if the zone data can not be parsed. ACKNOWLEDGEMENTS
This package is designed as an improved and compatible replacement for Net::DNS::ZoneFile 1.04 which was created by Luis Munoz in 2002 as a separate CPAN module. The present implementation is the result of an agreement to merge our two different approaches into one package integrated into Net::DNS. The contribution of Luis Munoz is gratefully acknowledged. Thanks are also due to Willem Toorop for his constructive criticism of the initial version and invaluable assistance during testing. COPYRIGHT
Copyright (c)2011-2012 Dick Franks All rights reserved. This program is free software; you may redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
perl, Net::DNS, Net::DNS::Domain, Net::DNS::RR, RFC1035 Section 5.1, RFC2308, BIND 9 Administrator Reference Manual perl v5.16.3 2012-12-28 Net::DNS::ZoneFile(3)
All times are GMT -4. The time now is 08:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy