On Mon, Sep 27, 2010 at 13:27, Brent L. Bates blba...@vigyan.com wrote:
Just noticed something. Have your serial number reflect the date you
last updated the file. That way you will know when you last changed it. For
example, today is September 27, 2010, if you were making your first
On Sat, Sep 25, 2010 at 18:15, Les Mikesell lesmikes...@gmail.com wrote:
For completeness: there is the BIND 9 Administrator Reference Manual,
known as the ARM, usually supplied under /usr/share/doc/.
And what many consider to be the standard reference, Liu and Albitz's
DNS and BIND published
I think you should be able to do this using BIND views with
match-destinations. Have one view match destinations for 1.1.1.1 and
1.1.1.2 and the other for 1.1.1.3 and 1.1.1.4. Create a zone in one
view for exampleA.com and one in the other for exampleB.com
Ryan
On Fri, Sep 24, 2010 at 1:08 PM,
On 9/24/10 11:12 PM, cpol...@surewest.net wrote:
On Fri, Sep 24, 2010 at 10:28:41PM +0200, Dotan Cohen wrote:
On Fri, Sep 24, 2010 at 22:24, Alexander Dallozad+li...@uni-x.org wrote:
http://www.zytrax.com/books/dns/
That is a good source to read up about bind configuration.
As a sidenote
On a CentOS 5 server, I am having a hard time configuring BIND to
answer to 4 IP addresses for 2 domain names.
Currently, I have four IP addresses, for sake of discussion they are:
1.1.1.1
1.1.1.2
1.1.1.3
1.1.1.4
Additionally, I have two domain names. For sake of discussion:
exampleA.com
- Original Message -
| On a CentOS 5 server, I am having a hard time configuring BIND to
| answer to 4 IP addresses for 2 domain names.
|
| Currently, I have four IP addresses, for sake of discussion they are:
| 1.1.1.1
| 1.1.1.2
| 1.1.1.3
| 1.1.1.4
|
| Additionally, I have two domain
Have a read for the listen on directive for BIND which tells BIND what
interfaces/IP Addresses to bind to.
Thanks, I am aware that Apache can be told to listen only to specific
addresses. Can BIND be told to listen on all addresses? Your post
implies that this is the default (which makes sense,
Maybe a Round-Robin configuration ?
2010/9/24 Dotan Cohen dotanco...@gmail.com
Have a read for the listen on directive for BIND which tells BIND what
interfaces/IP Addresses to bind to.
Thanks, I am aware that Apache can be told to listen only to specific
addresses. Can BIND be told to
On Fri, Sep 24, 2010 at 19:26, Eric Viseur eric.vis...@gmail.com wrote:
Maybe a Round-Robin configuration ?
Thank you Eric, but I may have been unclear. There is only one
physical server, but it answers to four IP addresses.
--
Dotan Cohen
http://gibberish.co.il
http://what-is-what.com
On 9/24/2010 12:21 PM, Dotan Cohen wrote:
Have a read for the listen on directive for BIND which tells BIND what
interfaces/IP Addresses to bind to.
Thanks, I am aware that Apache can be told to listen only to specific
addresses. Can BIND be told to listen on all addresses? Your post
implies
On Fri, Sep 24, 2010 at 19:38, Les Mikesell lesmikes...@gmail.com wrote:
You are making it much more complicated than necessary.
That is what I suspected! I know that when Linux gets difficult, it is
because I'm doing it wrong!
I'd configure
apache to use named virtual hosts and listen on
- Original Message -
| Have a read for the listen on directive for BIND which tells BIND
| what
| interfaces/IP Addresses to bind to.
|
| Thanks, I am aware that Apache can be told to listen only to specific
| addresses. Can BIND be told to listen on all addresses? Your post
|
On 9/24/2010 12:43 PM, Dotan Cohen wrote:
and bind to listen on all addresses and
answer for all your domains.
So, then, the association of a FQDN with any particular IP address is
only done in the domain name's control panel where the nameservers are
set?
What's a control panel? Bind is
On Fri, Sep 24, 2010 at 19:49, James A. Peltier jpelt...@sfu.ca wrote:
BIND has listen on directives as well, but if this is a single box
configuration
it's not necessarily required as it will listen on all interfaces.
Yes, I actually do want it to listen on all addresses (only one NIC),
I
On Fri, Sep 24, 2010 at 19:59, Les Mikesell lesmikes...@gmail.com wrote:
What's a control panel?
It is the web-based interface for the domain name registrar, in which
one configures the name servers for the domain name that he bought
from them.
Bind is going to want a zone file for each
On 9/24/2010 1:07 PM, Dotan Cohen wrote:
But any
instance of bind can be primary for any number of domains. The
association with the IP address(es) that will receive the queries
happens when you register the domain into the public dns system and you
can register the same server(s) as
On Fri, Sep 24, 2010 at 20:18, Les Mikesell lesmikes...@gmail.com wrote:
Probably a waste of time. If anyone cares, they'll track down the
domain and IP range ownership anyway (there are sites that do it
automatically). So unless you've used company aliases in the domain
registration and
Thank you for all the help so far. To conclude:
I have one physical server that answers to the following IP addresses:
1.1.1.1
1.1.1.2
1.1.1.3
1.1.1.4
I need 1.1.1.1 1.1.1.2 to be the name servers for exampleA.com, and
1.1.1.3 1.1.1.4 to be the nameservers for exampleB.com. I have these
files:
- Original Message -
| Thank you for all the help so far. To conclude:
| I have one physical server that answers to the following IP addresses:
| 1.1.1.1
| 1.1.1.2
| 1.1.1.3
| 1.1.1.4
|
| I need 1.1.1.1 1.1.1.2 to be the name servers for exampleA.com, and
| 1.1.1.3 1.1.1.4 to be the
- Original Message -
| - Original Message -
| | Thank you for all the help so far. To conclude:
| | I have one physical server that answers to the following IP
| | addresses:
| | 1.1.1.1
| | 1.1.1.2
| | 1.1.1.3
| | 1.1.1.4
| |
| | I need 1.1.1.1 1.1.1.2 to be the name servers
On Fri, Sep 24, 2010 at 22:06, James A. Peltier jpelt...@sfu.ca wrote:
formatting for NS records is incorrect. It should just read
NS ns1.exampleA.com.
NS ns2.exampleA.com.
Thanks. (I added the periods)
where is your ns1.exampleA.com entry?
where is
Ah, some better examples here:
http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-bind-zone.html
How is this file:
# cat /var/named/exampleA.com.hosts
$ORIGIN exampleA.com.
$TTL 1h
exampleA.com. IN SOA ns1.exampleA.com. ns2.exampleA.com. (
1; Serial -
Am 24.09.2010 22:12, schrieb Dotan Cohen:
On Fri, Sep 24, 2010 at 22:06, James A. Peltier jpelt...@sfu.ca wrote:
formatting for NS records is incorrect. It should just read
NS ns1.exampleA.com.
NS ns2.exampleA.com.
Thanks. (I added the periods)
At Fri, 24 Sep 2010 19:43:11 +0200 CentOS mailing list centos@centos.org
wrote:
On Fri, Sep 24, 2010 at 19:38, Les Mikesell lesmikes...@gmail.com wrote:
You are making it much more complicated than necessary.
That is what I suspected! I know that when Linux gets difficult, it is
because
At Fri, 24 Sep 2010 21:05:25 +0200 CentOS mailing list centos@centos.org
wrote:
On Fri, Sep 24, 2010 at 20:18, Les Mikesell lesmikes...@gmail.com wrote:
Probably a waste of time. Â If anyone cares, they'll track down the
domain and IP range ownership anyway (there are sites that do it
On Fri, Sep 24, 2010 at 22:24, Alexander Dalloz ad+li...@uni-x.org wrote:
http://www.zytrax.com/books/dns/
That is a good source to read up about bind configuration.
As a sidenote please be aware, that if someone directly queries your
ns1.exampleA.com for exampleB.com zone records he will
On Fri, Sep 24, 2010 at 22:24, Robert Heller hel...@deepsoft.com wrote:
Which is still meaningless. Some name servers serve *hundreds* of web
sites, many competing with each other. Often large hosting companies
will serve hundreds of web sites, all with the *same* IP address and
many in
On Fri, Sep 24, 2010 at 22:24, Robert Heller hel...@deepsoft.com wrote:
So, then, the association of a FQDN with any particular IP address is
only done in the domain name's control panel where the nameservers are
set?
It is in bind's database (zone files). In named.conf you associate
At Fri, 24 Sep 2010 21:58:09 +0200 CentOS mailing list centos@centos.org
wrote:
Thank you for all the help so far. To conclude:
I have one physical server that answers to the following IP addresses:
1.1.1.1
1.1.1.2
1.1.1.3
1.1.1.4
I need 1.1.1.1 1.1.1.2 to be the name servers for
At Fri, 24 Sep 2010 22:12:44 +0200 CentOS mailing list centos@centos.org
wrote:
On Fri, Sep 24, 2010 at 22:06, James A. Peltier jpelt...@sfu.ca wrote:
formatting for NS records is incorrect. Â It should just read
         NS ns1.exampleA.com.
       Â
On 9/24/2010 3:39 PM, Dotan Cohen wrote:
On Fri, Sep 24, 2010 at 22:24, Robert Hellerhel...@deepsoft.com wrote:
So, then, the association of a FQDN with any particular IP address is
only done in the domain name's control panel where the nameservers are
set?
It is in bind's database (zone
On Fri, Sep 24, 2010 at 22:41, Robert Heller hel...@deepsoft.com wrote:
You need:
ns1.exampleA.com. IN A 1.1.1.1
ns2.exampleA.com. IN A 1.1.1.2
Here I have found conflicting information, it seems that some sources
suggest this instead:
ns1 IN A
On Fri, Sep 24, 2010 at 22:41, Robert Heller hel...@deepsoft.com wrote:
With the rest of the IN A records for exampleA.com (and correspondingly
for exampleB.com). You need *addresses* for your name servers as well
as for your web servers.
I see.
And you might also want to have www.mumble
On Fri, Sep 24, 2010 at 22:47, Les Mikesell lesmikes...@gmail.com wrote:
I think that's reasonable - but note that from the rest of the world's
perspective the ns1, ns2 IP's are going to come from the glue records
from the upstream DNS that would have been added when you registered the
servers
- Original Message -
| On Fri, Sep 24, 2010 at 22:41, Robert Heller hel...@deepsoft.com
| wrote:
| You need:
|
| ns1.exampleA.com. IN A 1.1.1.1
| ns2.exampleA.com. IN A 1.1.1.2
|
|
| Here I have found conflicting information, it seems that some sources
| suggest this instead:
| ns1
- Original Message -
| - Original Message -
| | On Fri, Sep 24, 2010 at 22:41, Robert Heller hel...@deepsoft.com
| | wrote:
| | You need:
| |
| | ns1.exampleA.com. IN A 1.1.1.1
| | ns2.exampleA.com. IN A 1.1.1.2
| |
| |
| | Here I have found conflicting information, it seems
On Fri, Sep 24, 2010 at 23:13, James A. Peltier jpelt...@sfu.ca wrote:
| You need:
|
| ns1.exampleA.com. IN A 1.1.1.1
| ns2.exampleA.com. IN A 1.1.1.2
|
|
| Here I have found conflicting information, it seems that some sources
| suggest this instead:
| ns1 IN A 1.1.1.1
| ns2 IN A
On 9/24/2010 4:02 PM, Dotan Cohen wrote:
On Fri, Sep 24, 2010 at 22:41, Robert Hellerhel...@deepsoft.com wrote:
You need:
ns1.exampleA.com. IN A 1.1.1.1
ns2.exampleA.com. IN A 1.1.1.2
Here I have found conflicting information, it seems that some sources
suggest this
All right, I think this should do it:
$ORIGIN exampleA.com.
$TTL 86400
exampleA.com. IN SOA ns1.exampleA.com. ns2.exampleA.com. (
2; Serial - increment me
10800
3600
604800
- Original Message -
| All right, I think this should do it:
|
| $ORIGIN exampleA.com.
| $TTL 86400
| exampleA.com. IN SOA ns1.exampleA.com. ns2.exampleA.com. (
| 2; Serial - increment me
| 10800
| 3600
| 604800
| 38400 )
| IN NS ns1.exampleA.com.
| IN NS ns2.exampleA.com.
| IN A
On Fri, Sep 24, 2010 at 23:29, James A. Peltier jpelt...@sfu.ca wrote:
Looks good. you can change your 10800 3600 604800 and 38400 to hours, days
or weeks represented by 1h, 1d or 1w respectively to make it easier than
calculating seconds. :)
Thank you!
--
Dotan Cohen
At Fri, 24 Sep 2010 23:02:21 +0200 CentOS mailing list centos@centos.org
wrote:
On Fri, Sep 24, 2010 at 22:41, Robert Heller hel...@deepsoft.com wrote:
You need:
ns1.exampleA.com. IN Â Â Â A Â Â Â 1.1.1.1
ns2.exampleA.com. IN Â Â Â A Â Â Â 1.1.1.2
Here I have found
On Sat, Sep 25, 2010 at 00:06, Robert Heller hel...@deepsoft.com wrote:
When you have an $ORIGIN statement, it defines a suffix to automatically
add to any name that does not end in a '.'. You can do either,
depending on how gratiously verbose you want to be. Of course, being
verbose sort of
On Fri, Sep 24, 2010 at 10:28:41PM +0200, Dotan Cohen wrote:
On Fri, Sep 24, 2010 at 22:24, Alexander Dalloz ad+li...@uni-x.org wrote:
http://www.zytrax.com/books/dns/
That is a good source to read up about bind configuration.
As a sidenote please be aware, that if someone directly
44 matches
Mail list logo
