> -----Original Message-----
> From: Wikked Skye
> Sent: Sunday, March 30, 2003 9:15 AM
> Subject: RE: NameServers, DNS, and BIND
>
>
Why registrars' are allowing tld name servers to point NS records to the
same IP is beyond me. Gzzz!!! Where's the redundency?
[EMAIL PROTECTED] scowles]$ dig @a.gtld-servers.net mystyka.com ns
; <<>> DiG 9.2.1 <<>> @a.gtld-servers.net mystyka.com ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44303
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUESTION SECTION:
;mystyka.com. IN NS
;; ANSWER SECTION:
mystyka.com. 172800 IN NS ns1.mystyka.com.
mystyka.com. 172800 IN NS ns3.mystyka.com.
;; ADDITIONAL SECTION:
ns1.mystyka.com. 172800 IN A 64.91.118.88
ns3.mystyka.com. 172800 IN A 64.91.118.88
;; Query time: 77 msec
;; SERVER: 192.5.6.30#53(a.gtld-servers.net)
;; WHEN: Sun Mar 30 10:24:00 2003
;; MSG SIZE rcvd: 97
See my inserts below.
> Michael,
>
> Thanks for your help so far. Here is a copy of my named.conf file.
>
> Kelly
> ## named.conf - configuration for bind
> #
> # Generated automatically by redhat-config-bind, alchemist et al.
> # Any changes not supported by redhat-config-bind should be put
> # in /etc/named.custom
Although I have never used redhats config-bind program; I have found that
most utilites like this are lagging behind a few revisions. I never use
them.
> #
> controls {
> inet 127.0.0.1 allow { localhost; } keys { rndckey; };
> };
>
> include "/etc/named.custom";
So did you add any custom zone info to named.custom?
>
> include "/etc/rndc.key";
Did you generate your key? Don't use the one supplied with your redhat rpm.
>
> options {
> directory "/var/named/";
> };
>
>
>
> zone "mystyka.com" {
> type slave;
> file "mystyka.com.zone";
> masters {
> 64.91.118.88;
> };
> };
If your trying to setup a master name server, why are you listing
mystyka.com as a slave? Plus, the master is the same IP.
>
> zone "0.0.127.in-addr.arpa" {
> type master;
> file "0.0.127.in-addr.arpa.zone";
> };
Looks OK if the zone file is correct.
> zone "118.91.64.in-addr.arpa" {
> type master;
> file "118.91.64.in-addr.arpa.zone";
Why are you loading this zone when your TLD (ISP) has not delegated the
reverse lookup for this ip to your server. You can load this, but it will
never be queried by anyone on the internet until your ISP delegates this ip
to your server. Good Luck! My ISP will not delegate reverse lookups to my
name server.
> };
>
>
> zone "localhost" {
> type master;
> file "localhost.zone";
> };
Looks OK if the zone file is correct.
> zone "mystyka.com" {
> type master;
> file "mystyka.com.zone";
> };
OK, make up your mind. Now your loading mystyka.com as a master. Which is
correct based on the stated goal of your post, but you still have the zone
loading as a slave above. Bzzt!
FWIW: I have never configured a nameserver where both NS records point to
the same IP, but I would think you would want to load a single zone (as
master) but list both NS records. ie. Something like...
------------- /etc/named.conf ---------------
key "rndc-key" {
algorithm hmac-md5;
secret "hJ... key removed";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
options {
directory "/var/named";
listen-on { 127.0.0.1 ; 64.91.118.88; };
};
logging {
channel xfer-log {
file "/var/log/named/bind-xfer.log";
print-category yes;
print-severity yes;
print-time yes;
severity info;
};
category xfer-in { xfer-log; };
category xfer-out { xfer-log; };
category notify { xfer-log; };
category lame-servers{ null; };
};
###################################################
# Define External View Space
###################################################
view "external" {
# Allow all internet ip's to query this server/view.
match-clients { any; };
# But do NOT allow others to use my name server for recursive
# queries.
recursion no;
# Load mystyka.com as a master zone.
zone "mystyka.com" in {
type master;
# Since both NS IP's are pointing to this server...
notify no;
allow-update { none; };
# Since both NS IP's are pointing to this server...
# allow-transfer { xx.xx.xx.xx; };
file "ext/db.mystyka";
};
# Other zones below...
};
;##############################################################
; Start of Authority for mystyka.com.
; Filename: db.mystyka
;##############################################################
$TTL 1d
@ 7d IN SOA ns1.mystyka.com. (
netadmin.mystyka.com.
2002100208 ; serial
1h ; refresh
30m ; retry
7d ; expire
1h ) ; negative cache
;############################################################
; mystyka.com Nameserver Records (NS)
;############################################################
@ 7d IN NS ns1.mystyka.com.
@ 7d IN NS ns3.mystyka.com.
;############################################################
; mystyka.com Address Records (A)
;############################################################
localhost 1d IN A 127.0.0.1
; Name Server (glue) records
ns1 1d IN A 64.91.118.88
ns3 1d IN A 64.91.118.88
; Web/Internet based records
www 1d IN A 64.91.118.88
ftp 1d IN A 64.91.118.88
mail 1d IN A 64.91.118.88
smtp 1d IN A 64.91.118.88
;############################################################
; mystyka.com A (ADDRESS) and MX Records (MAIL EXCHANGER)
;############################################################
@ 1d IN A 64.91.118.88
@ 1d IN MX 0 mail.mystyka.com.
---------------------
Steve Cowles
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
