Do they all actually use separate IPs?
Here we have multiple domains that all go to the same web server many of
which are going to the same NATed IP. For those we just create a zone
(e.g. okstate-aliases) with standard setup and then the A record we have
is for @ like:
@ IN SOA dns1.okstate.edu. tech.okstate.edu. (
2010020501 ; serial
10800 ; refresh
3600 ; retry
604800 ; expire
86400 ) ; Minimun TTL
; Name Servers
;
IN NS dns1.okstate.edu.
IN NS dns2.okstate.com.
;
; Mail Servers
;
IN MX 10 mail1.okstate.edu. ; Primary MX BH
IN MX 30 mail2.okstate.edu. ; Primary MX BH
;
; Addresses
;
;
@ IN A x.x.x.x
;
In named.conf we would then add each domain to use this file like:
zone "okistatelab.com" {
type master;
file "okistate-aliases";
allow-query { any; };
};
The @ in the aliases file is interpreted as which ever zone is
referencing it so for that zone it becomes okistatelab. You can create
as many entries as you want pointing to that single aliases zone file.
For one offs you can simply copy the zone file to a new name and add
what you want (e.g. if you wanted to have separate MX records or add ftp
site etc...) then use that file in the named.conf.
Of course this works because our web server setup redirects things to
the appropriate landing pages or sites. (Most of our aliases go to our
default web site but we do have some landing pages for specialized
purposes.)
-----Original Message-----
From: bind-users-bounces+jlightner=water....@lists.isc.org
[mailto:bind-users-bounces+jlightner=water....@lists.isc.org] On Behalf
Of Martin McCormick
Sent: Tuesday, June 15, 2010 12:53 PM
To: bind-us...@isc.org
Subject: the one A record that must be in a Zone
We have our main domain of okstate.edu plus a ton of
non-okstate.edu names that we serve because someone purchased
the name. Each of these small zones has per haps one or two A
records and 99.9% of the time, the A records are redundant A
records that are the same as some host on our okstate.edu zone.
This is because one appears to need at least 1 A record in a
given zone. Example:
If we have orange.com and the server is
web27.okstate.edu, I must create an A record for orange.com
using web27's IP address rather than using a CNAME record to
point to web27. If I try that, we get the error that orange.com
has no A record.
Is there any kind of dummy A record one can stuff in to
a zone which satisfies this requirement such that one can then
use aliases or CNAME records for the valid hosts in the zone?
What has happened here is that a bunch of servers are
moving to a new subnet and, you guessed it, they are festuned
with redundant A records for these small zones. It is
going to be a lot of manual work to move them over, but I am
hoping it is a teachable moment in which there may be a better
way to do this so next time, all we do is move addresses and the
rest just keeps working.
Thanks for any and all suggestions.
Martin McCormick
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Proud partner. Susan G. Komen for the Cure.
Please consider our environment before printing this e-mail or attachments.
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential
information and is for the sole use of the intended recipient(s). If you are
not the intended recipient, any disclosure, copying, distribution, or use of
the contents of this information is prohibited and may be unlawful. If you have
received this electronic transmission in error, please reply immediately to the
sender that you have received the message in error, and delete it. Thank you.
----------------------------------
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
