Is this scenario possible?
Blason R
blason16 at gmail.com
Sat Jan 11 19:59:25 UTC 2014
Hey all,
Pertaining to the same discussion. Can someone validate below zone files
and named.conf files? What I wanted to achieve here is; I wanted to make
mail.example.com as my sub domain and give them A record so that I could
load balance the traffic on LBs since my LBs are offering inbuilt DNS server
example.com
NS = ns1.example.com 1.1.1.1
ns2.example.com 2.2.2.2
#############################################
#
# example.com MAIN ZONE FILE
#
#############################################
zone "example.com" in{
type master;
file "master/master.example.com";
// explicitly allow slave zone transfer
allow-transfer {2.2.2.2;};
};
##################################
#
# master.example.com
##################################
$TTL 2d
$ORIGIN example.com.
@ IN SOA ns1.example.com. hostmaster.example.com. (
2003080800 ; serial number
2h ; refresh = 2 hours
15M ; update retry = 15 minutes
3W12h ; expiry = 3 weeks + 12 hours
2h20M ; minimum = 2 hours + 20 minutes
)
IN NS ns1.example.com.
IN NS ns2.example.com.
IN MX 10 mx01.example.com.
IN MX 20 mx02.example.com.
ns1 IN A 1.1.1.1
ns2 IN A 2.2.2.2
; A record for mail server above
mx01 IN A 20.20.20.20
mx02 IN A 30.30.30.30
#######################################################
$ORIGIN mail.example.com.
@ IN NS ns3.mail.example.com.
; the next name server points to ns1 in the example.com zone above
IN NS ns1.example.com.
; sub-domain address records for name server only - glue record
ns3 IN A 20.20.20.21 ; 'glue' record
******************************************************
******************************************************
#############################################
#
# mail.example.com MAIN ZONE FILE
#
#############################################
zone "mail.example.com" in{
type master;
file "master/master.mail.example.com";
};
#############################################
# mail.example.com zone file
#############################################
#
$TTL 2d ; default TTL = 2 days
$ORIGIN mail.example.com.
@ IN SOA ns3.mail.example.com.
hostmaster.mail.example.com. (
2003080800 ; serial number
2h ; refresh = 2 hours
15M ; update retry = 15 minutes
3W12h ; expiry = 3 weeks + 12 hours
2h20M ; minimum = 2 hours + 20 minutes
)
; sub-domain name servers
IN NS ns3.mail.example.com.
; A records for name servers above
ns3 IN A 20.20.20.21
; A record for mail server above
mail IN A 20.20.20.20
mail IN A 30.30.30.30
On Thu, Jan 9, 2014 at 9:56 PM, Barry Margolin <barmar at alum.mit.edu> wrote:
> In article <mailman.1978.1389240374.20661.bind-users at lists.isc.org>,
> Blason R <blason16 at gmail.com> wrote:
>
> > Hey Guys,
> >
> > lets say I have a domain exmaple.com which is hosted out and are having
> MX
> > records as mail01.exmaple.com and mail02.example.com and
> > mail.example.comas a "A" Record for accessing mails
> >
> > example.com NA ns1.example.com
> > ns2.example.com
> >
> > IN MX mail01.example.com 10
> > mail02.example.com 20
> > mail.example.com IN A 1.1.1.1
> >
> >
> > Now I would like to create sub-domain as mail.exmaple.com and would
> like to
> > move that inside in my network on Bind while original NS are still with
> > exmaple.com.
> >
> > So for zone mail.example.com MX would be mail01.example.com &
> > mail02.example.com and A record again same as @
> >
> > What glitches do you see here by creating sub-domain mail.example.com
>
> As long as you move the above A record into the subdomain, I don't see
> any problem with this.
>
> You should also make sure you're more careful when editing your real
> zone files than you have been when writing your post, there were LOTS of
> typoes (NA instead of NS, exmaple for example). :)
>
> --
> Barry Margolin
> Arlington, MA
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20140112/8c21c8e3/attachment.html>
More information about the bind-users
mailing list