I have a couple of zone conf files for the BIND server.
There are some records that contains the "IN" statement and some do not.
But anyway this works.
So my question is what this "IN" is intended for?
Here is the zone file example:
Hi,
I have a primary/slave Bind 9 setup running on a Solaris 10 platform. Everything is hunky dorey, except for when I make a zone file change and up the serial the file that is transferred to the slave looses all its comments, and the entries are place in alphabetical order.
I administer many... (1 Reply)
Hello,
I have a question about dns file zone.
Every zone file begins like:
@ 86400 IN SOA ns1.website.com. admin@website.com. (
It means that name server ns1 is responsible for this zone.
At the ending I can add the records like
mysite.com IN A 1.2.3.4
So it will... (2 Replies)
I'd like to get some opnions on choosing DNS server:
Windows DNS vs Linux BIND comparrsion:
1) managment, easy of use
2) Security
3) features
4) peformance
5) ??
I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Hello all,
I have configured Freebsd 8.1 Bind DNS as DNS server for intrenal domain and clients on one subnet 192.168.10.0/24 . What do I have to change in zone file and in in-addr.arpa zone file if I have two additional subsets 192.168.20.0/24 and 192.168.30.0/24? Do I have to create another... (0 Replies)
Hy guys, I've a problem configuring my Name Server (using bind 9) which is I'ts always necessary to put all slave Name Server for a zone in the zone resource record file or db (as you prefer)?
I've this scenario:
A - my domain which is son of some TLD and I delegated into two new domains B... (1 Reply)
Hi all,
I have some sort of problem with BIND DNS server my environment as follows.
bash-3.00# cat /etc/release
Solaris 10 6/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to... (3 Replies)
We are currently using the famous script H2N to create our DNS zone files from a host file. However, we are moving to IPV6 soon and this script doesnt support IPV6. Is there another script/solution to creating DNS zones via a host file input? (0 Replies)
We are currently using the famous script H2N to create our DNS zone files from a host file. However, we are moving to IPV6 soon and this script doesnt support IPV6. Is there another script/solution to creating DNS zones via a host file input? Is there another solution or way to do things that I may... (0 Replies)
Discussion started by: jpolachak
0 Replies
LEARN ABOUT DEBIAN
oidentd_masq.conf
oidentd_masq.conf(5) File Formats Manual oidentd_masq.conf(5)NAME
oidentd_masq.conf - oidentd IP masquerading/NAT configuration file.
DESCRIPTION
If you are using IP masquerading or NAT, oidentd can optionally return a username for connections from other machines. Support for this is
specified by calling oidentd with the -m (or --masq) flag and by creating an /etc/oidentd_masq.conf file.
oidentd can also forward requests for an IP masqueraded connection to the machine from which connection originates by way of the -f option.
This will only work if the host to which the connection is forwarded is running oidentd with the -P (proxy) flag, or if the host's ident
daemon will return a valid reply regardless of the input supplied by and the address of the host requesting the info (some ident daemons
for windows do this, maybe others).
FORMAT
<IP Address|Hostname>[/<Mask>] <Ident Response> <System Type>
The first field contains the IP address or the hostname of a machine that IP masquerades through the machine on which oidentd runs. The
mask parameter can be either a network mask or a mask in CIDR notation. A mask of 24 is equivalent to 255.255.255.0, a mask of 16 is
equivalent to 255.255.0.0, etc.
The second field specifies the reply that oidentd will return for lookups to the host matching the IP address specified in the first param-
eter.
The third field specifies the operating system the machine matching the first parameter is running.
EXAMPLES
<Host>[/<Mask>] <Ident Response> <System Type>
192.168.1.1 someone UNIX
192.168.1.2 noone WINDOWS
192.168.1.1/32 user1 UNIX
192.168.1.0/24 user3 UNIX
192.168.0.0/16 user4 UNIX
somehost user5 UNIX
192.168.1.0/255.255.255.0 user6 UNIX
AUTHOR
Ryan McCabe <ryan@numb.org>
http://dev.ojnk.net
SEE ALSO oidentd(8)oidentd.conf(5)version 2.0.8 13 Jul 2003 oidentd_masq.conf(5)