Reverse DNS problem
RJHM van den Bergh
rvdb at nedernet.nl
Fri Nov 26 02:22:04 UTC 1999
Hi,
I got the answer from someone , and now it works.
I've pasted the info that helped me below.
Because I don't know if the person also replied to this newsgroep.
So when someone does a querry using dejanews for example he can perhaps
solve his problem to.
At the end I'll paste some of my new config files.
dig axfr 205.204.212.in-addr.arpa @ns1.widexs.nl | grep alpha.comweb.nl
100 1D IN NS alpha.comweb.nl.
91 1D IN NS alpha.comweb.nl.
92 1D IN NS alpha.comweb.nl.
93 1D IN NS alpha.comweb.nl.
94 1D IN NS alpha.comweb.nl.
95 1D IN NS alpha.comweb.nl.
96 1D IN NS alpha.comweb.nl.
97 1D IN NS alpha.comweb.nl.
98 1D IN NS alpha.comweb.nl.
99 1D IN NS alpha.comweb.nl.
While your provider has set thing up legally this is not the usual way
it is done.
To get this working you need to create 10 zones:
91.205.204.212.in-addr.arpa to 100.205.204.212.in-addr.arpa
Each of these then contains:
@ SOA alpha.comweb.nl. root.comweb.nl. ( .... )
NS alpha.comweb.nl.
PTR <hostname for relevent IP>
e.g.
named.reverse91:
@ SOA alpha.comweb.nl. root.comweb.nl. (
1999112600 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D) ; Minimum TTL
NS alpha.comweb.nl.
PTR alpha.comweb.nl.
The usual way to do this would be to delegate
91-100.205.204.212.in-addr.arpa (or similar) and make
91.205.204.212.in-addr.arpa though 100.205.204.212.in-addr.arpa
CNAME records pointing into 91-100.205.204.212.in-addr.arpa.
e.g.
91-100.205.204.212.in-addr.arpa NS alpha.comweb.nl.
91.205.204.212.in-addr.arpa. CNAME 91.91-100.205.204.212.in-addr.arpa.
...
100.205.204.212.in-addr.arpa. CNAME 100.91-100.205.204.212.in-addr.arpa.
Also take care as you had "in.addr.arpa" not "in-addr.arpa" below.
A period instead of a hyphen.
Mark
(Thank you)
--------
Here my new working config files
[root at alpha named]# cat named.reverse91
$ORIGIN 91.205.204.212.in-addr.arpa.
@ IN SOA alpha.comweb.nl. root.comweb.nl. (
199911261 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D) ; Minimum TTL
;
NS alpha.comweb.nl.
PTR alpha.comweb.nl.
;
[root at alpha named]#
[root at alpha named]# cat /etc/named.conf
options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
// IP nummers assigned 212.204.205.91-100
zone "." {
type hint;
file "named.ca";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "named.local";
};
zone "comweb.nl" {
notify yes;
type master;
file "named.comweb.nl";
};
zone "91.205.204.212.in-addr.arpa" {
notify yes;
type master;
file "named.reverse91";
};
zone "92.205.204.212.in-addr.arpa" {
etceteras ...
Rob,
rvdb at nedernet.nl
RJHM van den Bergh <rvdb at nedernet.nl> wrote in message
news:943558936.8279.0.pluto.c29fe22b at news.demon.nl...
> Hi
>
> I asked my provider to run my own DNS using RFC 2317
> They say they have adjusted their DNS so I had to set up reverse DNS.
>
> All works fine except reverse DNS.
>
>
> ----------------------------
> I got a whole bunch of errors from the /var/log/messages.
>
> Nov 25 22:13:33 alpha named[1290]: named.reverse91:4: SOA for "91.205.
> 204.212.in.addr.arpa" not at zone top "91.205.204.212.in-addr.arpa"
> (I just cant seem to get rid of this one.)
>
> Nov 25 22:13:33 alpha named[1290]: named.reverse91:11: data "91.205.20
> 4.212.in.addr.arpa" outside zone "91.205.204.212.in-addr.arpa" (ignore
> d)
> (This one I do understand it caused by the first)
> (There are of course several of them)
>
> Nov 25 22:13:33 alpha named[1290]: Zone "91.205.204.212.in-addr.arpa"
> (file named.reverse91): no NS RRs found at zone top
> Nov 25 22:13:33 alpha named[1290]: master zone "91.205.204.212.in-addr
> .arpa" (IN) rejected due to errors (serial 199802151)
> (Don't get this either. I stated the DNS servers)
> -----------------------
>
> Somehow I think the glue record isn't working.
> Think the reverse tree doesn't match
>
> When I do nslookup:
> > 91.90.205.204.212.in-addr.arpa.
> Server: localhost
> Address: 127.0.0.1
>
> 91.90.205.204.212.in-addr.arpa name = HOSTED-BY.widexs.nl
> 205.204.212.in-addr.arpa nameserver = ns1.widexs.nl
> 205.204.212.in-addr.arpa nameserver = ns2.widexs.net
> ns1.widexs.nl internet address = 212.204.192.252
> ns2.widexs.net internet address = 212.204.207.192
>
> It states that 212.205.204.91 is hosted by these DNS servers.
> This is the old situation !! ?
> My DNS server is alpha.comweb.nl
> second DNS server should be ns2.widexs.nl
>
> Am I still thinking correct ?
>
> ----------------
>
> Here are my current config files :
>
> --------------------------------- named.conf
>
> [root at alpha named]# cat /etc/named.conf
> options {
> directory "/var/named";
> /*
> * If there is a firewall between you and nameservers you want
> * to talk to, you might need to uncomment the query-source
> * directive below. Previous versions of BIND always asked
> * questions using port 53, but BIND 8.1 uses an unprivileged
> * port by default.
> */
> // query-source address * port 53;
> };
>
> // IP nummers assigned 212.204.205.91-100
>
> zone "." {
> type hint;
> file "named.ca";
> };
>
> zone "0.0.127.in-addr.arpa" {
> type master;
> file "named.local";
> };
>
> zone "comweb.nl" {
> notify no;
> type master;
> file "named.comweb.nl";
> };
>
> zone "91.205.204.212.in-addr.arpa" {
> notify no;
> type master;
> file "named.reverse91";
> };
>
> //
> // to do : notify should be yes
>
>
>
> -------------the reverse file
>
> [root at alpha named]# cat named.reverse91
> ;$ORIGIN comweb.nl.
> ;$ORIGIN 91.90.205.204.212.in.addr.arpa.
> $ORIGIN 91.205.204.212.in.addr.arpa.
> @ IN SOA alpha.comweb.nl. root.comweb.nl. (
> 199802151 ; Serial, todays date + todays serial
> 8H ; Refresh
> 2H ; Retry
> 1W ; Expire
> 1D) ; Minimum TTL
> ;
> @ IN NS alpha.comweb.nl.
> @ IN NS ns2.widexs.net.
> ;
> alpha.comweb.nl. A 212.204.205.91
> 91 PTR alpha.comweb.nl.
> 92 PTR HostedByComweb.nl.
> [root at alpha named]#
>
>
> -----------------------
> To make it complete my domain zone file:
> Works great I can checked that.
> Indeed I get the Hinfo and correct DNS servers returned.
>
> [root at alpha named]# cat named.comweb.nl
> @ IN SOA alpha.comweb.nl. root.comweb.nl. (
> 199802151 ; serial , todays date +todays serial #
> 8H ; refresh , seconds
> 2H ; retry , seconds
> 1W ; expire seconds
> 1D ) ; minimum, seconds
> ;
> NS alpha ; Inet address of server
> NS ns2.widexs.net. ;
> MX 10 mail.comweb.nl. ; Primairy Mail Exchanger
> ; Omited a Secondary Mail exchanger
> localhost A 127.0.0.1
> alpha A 212.204.205.91
> mail A 212.204.205.91
> HINFO "Pentium II" "Linux RedHat"
> MX 10 alpha
> * CNAME alpha
> ;www CNAME alpha
> ;ns A 212.204.205.91 ;temp. a local address
> ; MX 10 mail
> ;mail A 212.204.205.91
> ;
> [root at alpha named]#
>
> ----------------------------
>
>
> Did play arround with it all day and still can't get it to work.
> did try 90.91.205.204.212
> WHAT AM I DOING WRONG ??
>
> I'm using a RedHat 5.2 with Bind 8.2.2
>
> Also where can I find more info ?
> My books here just only talk about bind 4.9 which is quite confusing to
me.
>
> Thanks for a reply.
>
> Rob
> rvdb at nedernet.nl
> root at comweb.nl
> (hostmaster at comweb.nl :-) )
>
>
>
>
>
>
>
>
>
More information about the bind-users
mailing list